-
Bug
-
Resolution: Unresolved
-
Medium
-
11
-
Severity 3 - Minor
-
2
-
Summary
Set Resolution will not save in Configuration boards other than the built-in status (to-do, in progress and done)
Replicate
- Create new board project with simplified workflow scheme
- Create new status
- Go to Board Configuration > Column
- Tick on the "Set Resolution" checkbox of the new status
Expected
After refresh, the Set Resolution box are saved
Actual
After Refresh, The Set Resolution box doesn't save
Workaround
After looking at the built-in status/transition. All have an extra post function by default: "The Resolution of the issue will be set to Done."
Adding the new transition with the post function "The Resolution of the issue will be set to ANY." enables the Set Resolution functionality.
Example post function that adds a value to the Resolution field:
[JRACLOUD-94757] Set Resolution unable to save
I did manage to make to workaround work.
This helped
You need to create a "Transition" for the "Status"...
The Transition Types should be - Update a Field in the issue.
Then you can set the Resolution field to Done when the issue transitions to this status.
Still an issue for me also... and I don't really understand how to try the workaround... could it be made clearer please.
This is still an issue for me.
Also the work-around didn't work. I tried using the post-function to set the status to "Done" or "None" ("Any" is not a selectable option) but it didn't fix the issue. Plus it also removed the checkboxes entirely in the board columns settings.
All I want is for my rejected tickets to not appear to be open. My current work-around is to delete rejected tickets but I really don't like doing this, thanks.
This not only affects the little checkbox, but any reporting that is based on setting the resolution, this includes gadgets; I have not checked project reports but I suspect if they read from this field they will be affected also.
Setting ONLY the Closed transition to "The Resolution of the issue will be set to Done" seems to have fixed the problem for me.
Still an issue.
With this many comments over nine months, how has this still not been fixed?
Seeing this also for Data Center. I'm shocked this bug is over 4 years old.
Setting the Resolution field correctly is critical to proper UI behavior (key strikeout), reporting (including built-in reports), filters, and Jira Plan behavior. These are documented here.
Come on, Atlassian. This bug should not be ignored.