-
Suggestion
-
Resolution: Done
-
Debian Linux, standalone JIRA using mySQL 4.1 database.
-
2
-
5
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Hi everyone,
Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use JIRA so we can continue improving your experience. We have reviewed this issue over the last few days.
This suggestion is important for the JIRA development team, but we have not scheduled work and cannot provide an estimate on when it will be released. I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.
Regards,
Daniel Franz
dfranz at atlassian dot com
Principal Product Manager, JIRA Platform
Despite being set to Optional in the Field Configuration, the Resolution field always shows up as Required on any screen that includes it. This wouldn't be such a bad thing if it weren't for two things:
- it's not possible to select the Unresolved option (which would mean leaving the field empty);
- having any value set for Resolution makes the Issue to be considered resolved, and the Issue Key to be crossed out across JIRA.
I would like to request that either the Required/Optional flag in the Field Configuration be made to apply to the Resolution field, or allow us to select a built-in UNRESOLVED resolution.
- causes
-
JRACLOUD-39745 Adding the ‘Resolution’ field to the edit screen forces it to be set on every issue change
- Closed
- is related to
-
JRASERVER-7159 Make Resolution field optional
- Gathering Interest
- relates to
-
JRACLOUD-72428 Resolution is no longer mandatory by default when it's added to screen
- Closed
-
JRACLOUD-1971 Can't change resolutions without re-opening an issue
- Closed
-
JRACLOUD-29899 The 'Resolution' field can not retain original value during Bulk Close issue
- Closed
- mentioned in
-
Page Loading...