-
Suggestion
-
Resolution: Unresolved
-
377
-
61
-
Hello all, Thank you for watching, voting, and commenting on this issue. We use this data as well as many other inputs to feed into our prioritization process. Resolution field will be available in next-gen in the future; however, this is not something that will be focusing on in the next year. We want to share this with you to ensure you can plan out your use of projects within Jira Software effectively. In the short term, we shipped the ability to add multiple Done statuses and map multiple statuses to a single column. Please continue to vote and in particular please continue to add comments on how your teams find value in the resolution field. This contextual information of what you are doing and why you are doing is invaluable for us in providing you with a product that will grow with your needs. Thank you, Bryan Lim Product Manager
Problem definition
Currently, when transitioning an issue to right-most column of a board, it set's the Done resolution.
Suggested Solution
Add the ability to customize which Resolution is going to be set by Board Rules or drop-down list with the options, for example, Won't Do or Duplicate, or removing the resolution flag altogether.
- is duplicated by
-
- Closed
- is related to
-
- Gathering Interest
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
[JRACLOUD-92747] Customize Resolution field in team-managed projects
For anyone wondering you can clear and set resolution via automation. It's dumb, but can be done. Though it's merely a workaround for a silly limitation that needs to be fixed.
- To set resolution via automation
You can use automation and simply edit the resolution field. - To un-set resolution via automation
You have to use the "additional fields" editor for some reason with the code below.
{
"fields":
}
To effectively use Jira we need basic functionality like this. If you can offer this in Company managed I do not understand why you cannot do this change.
Jira keeps increasing costs but forget basic functionalities needed. Please review.
We use the resolution field to determine the reason why an issue was Closed or Done. This is also used in reporting to determine how many genuine defects raised. Seems to be pretty standard functionality. Examples below of some we use for a defect.
- Fixed
- Duplicate
- Descoped
- Cannot reproduce
- Test data error
- Not a defect
f5e3e1c5daad one problem with that method or using any automation to set resolution (which we also do), is that you can never clear it once it is set. Unfortunately, you cannot clear a resolution via API and can only do it in a classic workflow's post function. Team Managed Projects would be cooler if just a few features were added (set/clear resolution, share global fields including Story Points, etc.).
You can create a manually triggered automation to update the resolution instead of using the status
Team managed projects...
Where ALL work is completed
Never a "won't do"!
I have never seen a team that can positively complete every single ticket that comes their way....must be awesome! However most of us mortals need to be able to close a ticket in ways other than "done".
It's interesting please!