-
Bug
-
Resolution: Fixed
-
High
-
None
-
49
-
Severity 3 - Minor
This has been fixed and released to everyone 
Any issues moved to/from the 'done' status category from now on will have their resolution set or cleared correctly.
Something to note is that this will not be applied to historical data, any issues already in the 'done' category will not have their resolution automatically set to resolved. We were worried about the impact of making such a mass change to all projects' 'done' issues, so have left the decision to you if you wish to do a one-off update.
To do so, you can use Jira's bulk edit feature to update the resolution to 'resolved', you will only need to do this once, and any future updates will happen automatically. Follow the steps listed under the 2. Transition your issues heading here - https://confluence.atlassian.com/jirakb/bulk-update-the-resolution-field-in-jira-321857142.html#BulkupdatetheresolutionfieldinJira-2.TransitionyourIssues
Issue Summary
In JWM projects we don't add resolution fields into our templates (we choose not to do it), however, this field is still visible in the issue navigator and might cause confusion. In CMP the customer can always create a post function to make this transition to resolved happens, but there is no workaround in TMP
Furthermore, the Created vs. Resolved and Created Issues reports built into the template will not reflect resolved issues because no resolution is set, and there is no option to do so aside from automation.
Steps to Reproduce
- Move a ticket to “done” or any status that means resolve
Expected Results
Resolution field to be resolved
Actual Results
The resolution field stays unresolved
Workaround
You can create an automation to change the value of the field Resolution to "Done", once the issue is transitioned to Done.
This is accessible via System » Global Automation
- is duplicated by
-
-
- Closed
-
- is related to
-
JWMCLOUD-23 Allow more than 1000 issues on JWM Boards
- Closed
-
- Gathering Interest
- relates to
-
- Closed
- is cloned by
-
DISTRO-790 Failed to load
[JWMCLOUD-180] TMP Resolution field does not change to resolve when issue move to done
| Remote Link | Original: This issue links to "JWMDISTRO-790 (Jira)" [ 730517 ] | New: This issue links to "DISTRO-790 (J-Bus)" [ 730517 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 771087 ] |
| Link |
New:
This issue relates to |
| Description |
Original:
{panel:title=Atlassian Update - May 2023|borderStyle=solid|borderColor=#3c78b5|titleBGColor=#3c78b5|bgColor=#e7f4fa}
Copied from this comment: This has been fixed and released to everyone :) Any issues moved to/from the 'done' status category from now on will have their resolution set correctly. Something to note is that this will not be applied to historical data, any issues already in the 'done' category will not have their resolution automatically set to resolved. We were worried about the impact of making such a mass change to all projects' 'done' issues, so have left the decision to you if you wish to do a one-off update. To do so, you can use Jira's bulk edit feature to update the resolution to 'resolved', you will only need to do this once, and any future updates will happen automatically. Follow the steps listed under the *2.* *Transition your issues* heading here - [https://confluence.atlassian.com/jirakb/bulk-update-the-resolution-field-in-jira-321857142.html#BulkupdatetheresolutionfieldinJira-2.TransitionyourIssues] {panel} h3. Issue Summary In JWM projects we don't add resolution fields into our templates (we choose not to do it), however, this field is still visible in the issue navigator and might cause confusion. In CMP the customer can always create a post function to make this transition to resolved happens, but there is no workaround in TMP Furthermore, the Created vs. Resolved and Created Issues reports built into the template will not reflect resolved issues because no resolution is set, and there is no option to do so aside from automation. h3. Steps to Reproduce # Move a ticket to “done” or any status that means resolve h3. Expected Results Resolution field to be resolved h3. Actual Results The resolution field stays unresolved h3. Workaround You can create an automation to change the value of the field Resolution to "Done", once the issue is transitioned to Done. This is accessible via *_System » Global Automation_* !Automation Resolution.png|thumbnail! |
New:
{panel:title=Atlassian Update - May 2023|borderStyle=solid|borderColor=#3c78b5|titleBGColor=#3c78b5|bgColor=#e7f4fa}
This has been fixed and released to everyone :) Any issues moved to/from the 'done' status category from now on will have their resolution set or cleared correctly. Something to note is that this will not be applied to historical data, any issues already in the 'done' category will not have their resolution automatically set to resolved. We were worried about the impact of making such a mass change to all projects' 'done' issues, so have left the decision to you if you wish to do a one-off update. To do so, you can use Jira's bulk edit feature to update the resolution to 'resolved', you will only need to do this once, and any future updates will happen automatically. Follow the steps listed under the *2.* *Transition your issues* heading here - [https://confluence.atlassian.com/jirakb/bulk-update-the-resolution-field-in-jira-321857142.html#BulkupdatetheresolutionfieldinJira-2.TransitionyourIssues] {panel} h3. Issue Summary In JWM projects we don't add resolution fields into our templates (we choose not to do it), however, this field is still visible in the issue navigator and might cause confusion. In CMP the customer can always create a post function to make this transition to resolved happens, but there is no workaround in TMP Furthermore, the Created vs. Resolved and Created Issues reports built into the template will not reflect resolved issues because no resolution is set, and there is no option to do so aside from automation. h3. Steps to Reproduce # Move a ticket to “done” or any status that means resolve h3. Expected Results Resolution field to be resolved h3. Actual Results The resolution field stays unresolved h3. Workaround You can create an automation to change the value of the field Resolution to "Done", once the issue is transitioned to Done. This is accessible via *_System » Global Automation_* !Automation Resolution.png|thumbnail! |
| Description |
Original:
{panel:title=Atlassian Update - March 2023|borderStyle=solid|borderColor=#3c78b5|titleBGColor=#3c78b5|bgColor=#e7f4fa}
Copied from [this comment|https://jira.atlassian.com/browse/JWMCLOUD-180?focusedCommentId=3254665&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-3254665]: Hi all! I am an engineering manager here at Atlassian and I am happy to say we have put this issue on our roadmap and will have the fix out to you before the end of June this year. {panel} h3. Issue Summary In JWM projects we don't add resolution fields into our templates (we choose not to do it), however, this field is still visible in the issue navigator and might cause confusion. In CMP the customer can always create a post function to make this transition to resolved happens, but there is no workaround in TMP Furthermore, the Created vs. Resolved and Created Issues reports built into the template will not reflect resolved issues because no resolution is set, and there is no option to do so aside from automation. h3. Steps to Reproduce # Move a ticket to “done” or any status that means resolve h3. Expected Results Resolution field to be resolved h3. Actual Results The resolution field stays unresolved h3. Workaround You can create an automation to change the value of the field Resolution to "Done", once the issue is transitioned to Done. This is accessible via *_System » Global Automation_* !Automation Resolution.png|thumbnail! |
New:
{panel:title=Atlassian Update - May 2023|borderStyle=solid|borderColor=#3c78b5|titleBGColor=#3c78b5|bgColor=#e7f4fa}
Copied from this comment: This has been fixed and released to everyone :) Any issues moved to/from the 'done' status category from now on will have their resolution set correctly. Something to note is that this will not be applied to historical data, any issues already in the 'done' category will not have their resolution automatically set to resolved. We were worried about the impact of making such a mass change to all projects' 'done' issues, so have left the decision to you if you wish to do a one-off update. To do so, you can use Jira's bulk edit feature to update the resolution to 'resolved', you will only need to do this once, and any future updates will happen automatically. Follow the steps listed under the *2.* *Transition your issues* heading here - [https://confluence.atlassian.com/jirakb/bulk-update-the-resolution-field-in-jira-321857142.html#BulkupdatetheresolutionfieldinJira-2.TransitionyourIssues] {panel} h3. Issue Summary In JWM projects we don't add resolution fields into our templates (we choose not to do it), however, this field is still visible in the issue navigator and might cause confusion. In CMP the customer can always create a post function to make this transition to resolved happens, but there is no workaround in TMP Furthermore, the Created vs. Resolved and Created Issues reports built into the template will not reflect resolved issues because no resolution is set, and there is no option to do so aside from automation. h3. Steps to Reproduce # Move a ticket to “done” or any status that means resolve h3. Expected Results Resolution field to be resolved h3. Actual Results The resolution field stays unresolved h3. Workaround You can create an automation to change the value of the field Resolution to "Done", once the issue is transitioned to Done. This is accessible via *_System » Global Automation_* !Automation Resolution.png|thumbnail! |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Progress [ 3 ] | New: Closed [ 6 ] |
| Assignee | New: Heather Roberts [ hroberts ] |
| Status | Original: Short Term Backlog [ 12074 ] | New: In Progress [ 3 ] |
| Support reference count | Original: 48 | New: 49 |
| Status | Original: Long Term Backlog [ 12073 ] | New: Short Term Backlog [ 12074 ] |