Using OnDemand there is a workflow template for software development projects (see https://confluence.atlassian.com/display/AOD/Software+Development+project). However, even when I press "Done" on an issue it transitions to the "Done" state but remains as "Resolution: Unresolved". Am I missing a step somewhere?
I did in fact submit a support request, and here's the response from David Nicholson:
"When you press 'Done', you're changing the status of the issue as you move it into a new workflow step, but that doesn't change the Resolution field automatically. If you would like that to happen, you'll need to add a post action to the transition to Done that updates the value of the Resolution field. Any value other than "Unresolved" will mean that there is a resolution, and it will show up properly on your reports and gadgets.
You can find details on Workflows at https://confluence.atlassian.com/display/AOD/Configuring+Workflow, and on Transitions and post actions by following the link to Advanced Workflow Configuration in the menu on the right hand side."
So my conclusion is that the pre-configured workflow, which I thought would be a good bootstrap for a new development project, isn't actually very useful since it never resolves or closes issues. So I guess I'll ignore it and take the time to configure a custom workflow for what should be a very ordinary process. Pity.
I filed a bug report: https://support.atlassian.com/browse/JST-82031
Note that the documentation states "When any 'Done' transition occurs the resolution is set to Done."
So this should definitely be considered a bug.
Agree with Tom. This should be treated as a bug or unfinished functionality, particulary since most JIRA reporting relies on issues transitioning to a Resolved state. All users of these stock workflows will need to make these customizations in order for reporting to be accurate.
Since it is a Software Development Workflow there is no resolution. You are creating something new, so at the end you simply say "done" - no need to set a resolution.
However, if you want to use this workflow to fix something and you require a resolution you will have to change the workflow (create a copy of the workflow). There are two options.
1. In the transition to done add a screen with resolution field (or if already a screen is used add the field to that screen) and use a field required validator for resolution. So everytime you set an issue to done the resolution must be set.
2. If you want always the same resolution (e.g. fixed) use a post function in that transition and set the resolution to e.g. fixed.
I may 'love' Jira - but this is a(nother) good example of how un-user-friendly it is - if you want to leave things like this in, working this way (correct or not), people are going to find it confusing and frustrating to use.
Still, until something else competes, this is still the only thing around so we will use it!
Default Workflows in Jira should resolve issues as they have a Post Function in the Done Transition to update the Resolution Field.
If your Workflow does not have such a post function, then you might be having this bug https://jira.atlassian.com/browse/JRA-36324that is just being fixed and will be deployed soon.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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