we have a few projects using a indivual workflow and NOT using the field "resolved"...
So every time we open the (new) issue navigator, the default filter "open issues" is selected and NO issue are found. This is a little bit irritating... is it possible to configure other default filters for those projects?
We currently use JIRA 6.4.11.
Code. You'll have to hack the code providing the panels and filters.
A far better alternative is to stop having projects that "don't use resolution", because you don't actually have them. You have projects that don't use resolution correctly and hence inadvertently break all the built in reporting (and it's not just JIRA Core, you'll have problems with applications and add-ons too).
Set the resolution with a post-function as an issue is "closed" and blank it on "re-open". Your users don't need to know you're doing it, but it fixes all the problems you're making with these projects.
Before this discussion starts i didn't think about to not set the resolution if the developer fix an issue (i should do that). That one need a resolution for all the filters, plugins, ... is a fact (i don't like it but one have to knot it. In my opinion to see if an issue is closed i have a status). One should use resolutions if the issue is closed.
There's no debate to be had in this case. The choices available are 1. Wait for Atlassian to change the "resolution = done" principle 2. Rewrite JIRA and its applications and add-ons yourself 3. Set resolution on moving into a "done" type status
The "default filter" does not depend on the Field "Resolution" - I can set it via a post-function, but that does not change the situation: that default filter does still not work! Only adding the field 'resolution" to the field configuration of the project solved my problem.
Well, I'd say it's very flexible, but that gives you complexity in using that flexibility.
I also think "resolution is empty/not empty" is a poor way to do this particular function. It was fine in JIRA 1 when there was only one workflow, but now we have the power to define our own, it looks pretty daft.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs