Few months ago i have made some WorkFlow modifications, in big lines all was ok till few days ago when one of my resp showed me this:
Several issues have a wrong resolution:
E.G: He showed me a issue with the Status TO DO and with the Fini = DONE Resolution... (see pics) or reversal issues with DONE Status has OPEN Resolution
The problem is in the Agile board the issue appears as DONE... this is not very helpful, and he already missed some issues because of that situation.
Before put here the question i have researched and found only questions without answers...
If any of you had a idea/solution... please share it with me
I think the search functions here are very weak, there are loads of answers on this subject
Cause: someone has put the resolution field on the edit (or create) screen for your issues, so the users are setting it (they can't leave it blank)
Fix part 1:
Fix part 2:
You now have a pile of broken issues that are open but resolved.
Hi Nick & Thank's
This is a very well detailed FIX, first i will remove all the resolution field from the screens (i will keep only for the Close and Done) and than (i will try the easy way) i will try do do what Sten said
We don't have a very large number of issues, we have +-30 Agile projects with a 200 max issues in each one, and i have found it only 2 projects with "bugs"
I really don't like to play with the workflows (even so when my resp asked me i have done it...) we use JIRA from about a year and i'm faaaaar away to be a guru/expert
I will keep you and Sten updated.
A big thank's for your fast answers.
As you can't edit the Resolution directly (at least I couldn't), you have to use a workaround. You can create a new transition from the status the ticket is in back onto itself and have the resolution field visible. Make the transition available only to yourself or to an administrator group.
Create a filter showing the issues in this status with incorrect resolution, then use Bulk Edit (Bulk Transition) to change the Resolution.
Rinse and repeat for every transition in which there are issues with this problem.
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