-
Sub-task
-
Resolution: Unresolved
-
Low
-
None
-
None
-
None
-
None
Problem Statement
Lack of "Resolution" value in JSD next gen is causing how issues appear in queue. If there is no resolution value set to the issues in a next gen sd project how would Jira recognize these issues as resolved? This affects how these issues appear in filters, the strike through of the resolved issues, etc.
More specifically:
- "Resolved" tickets still appear on open on customer portal.
- Issues do not have a Resovled date so the "Resolved" column on the queue is always empty.
Proposed Solution
Allow adding value to the "Resolution" field on JSD next gen issues.
- duplicates
-
JSDCLOUD-8082 Ability to add a resolution on tickets when using JSD next-gen
- Closed
-
JSDCLOUD-9761 Ability to set resolution on JSM next gen projects
- Closed
[JSDCLOUD-8523] Allow adding value to the "Resolution" field on JSD next gen issues.
Remote Link | Original: This issue links to "Page (Atlassian Documentation)" [ 952608 ] |
Remote Link | New: This issue links to "Page (Atlassian Documentation)" [ 952608 ] |
Link |
New:
This issue duplicates |
Assignee | New: Jehan Gonsalkorale [ a620038e6229 ] |
Assignee | Original: Kerry Wang [ f4c9f4d6e4c1 ] |
Assignee | New: Kerry Wang [ f4c9f4d6e4c1 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 671889 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 606911 ] |
Link |
New:
This issue duplicates |