There are some situations where it could be more constructive to leave the question open so it can be discussed even if it is bug related.
Several areas of Blender have multiple pathways and if one tool fails because of a bug, it is not necessarily the case that all available work-flow options will fail.
If a question like this is closed for being a report, alternate methods do not have a chance to be brought up by other people who have found a work-around that can accomplish the same task but in a different way.
Automatically sending people to the tracker without discussion can also lead to the tracker becoming filled with nuisance reports and this can lead to issues for developers who have enough work to do already without having to sort through issues that could have easily been dealt with here.
If a question is closed for this reason and there is no discussion on the topic; every time someone comes here with a similar issue, they will think that it has not already been discussed because the other similar questions are not available. Now the nuisance question is right back again and now it has to be closed.
Leaving them open or directing the user to a page where the problems have been linked together can help to prevent these types of questions from repeatedly being asked.
Enough bug reports have been moved onto a to-do list instead of being fixed right away and when this happens, alternative solutions have to be used.
Not every code problem is going to have an immediate solution, some may never have one.
In cases like this, artists discussing work-flow alternatives needed to work around these bugs is really the only available option.
The following example shows a bug report that is valid; However, if it had been brought up here(and left open), then it could have been a discussion on how to avoid the bug in the first place.
https://developer.blender.org/T42056
Coders and algorithm designers cannot bear the full weight for everything that can go wrong with a complex system of tools.
Artists should have multiple ways around software weaknesses so they are not tripped up when bugs are encountered.
It helps to know how to avoid encountering those situations to begin.
One way to learn these things can be to make bug-report related questions into discussions instead of closing them.
Now bug-reports can be focused on problems which cannot be solved by work-flow solutions.
There should be no hurry to shut them down and move on as quickly as possible. That goes for many of the other 'close' reasons unless they are spam or abusive.
A particular bug report discussion here can be good cross-reference for the actual bug report since artists showing up here may have something to contribute.
If an artist shows up here a few months after the question is posted and recognizes a pattern to the bug based on similar issues they've been having, it may now become solvable instead of sitting idle in the Tracker for several more months(or years).
If it's been discussed and decided upon that a serious bug is present, the person can be referred to the tracker and asked to post the tracker URL on the related page here on this site.
Now anyone who finds the page will also know where to find the bug report, but only if the page here is still open.
This brings more opportunity for the problem to be solved because there will be more people involved.
If a developer reports, on bug tracker, that the issue has been solved, the page here can then be reported as being no longer valid. Now it can be removed.
