-
Suggestion
-
Resolution: Unresolved
-
None
Issue
When a Jira issue is created from a Roadmap plan in the case where the default priority is set to "none" in the priority scheme, the way the issue is created is not consistent with how the issue is created via the normal Jira Create button, or via the JSM Customer Portal:
- in the case of the Jira Create button and the JSM Customer Portal, the issue will be created with a priority set (the priority listed in the middle of the priority scheme will be automatically chosen). -> This behavior is described in JRASERVER-70654
- however, in the case of Roadmap plans, the issue will be created without a priority
This is what the Priority scheme will look like, if "none" is selected:
Suggestion
Make sure that the way the "none" default priority is handled is consistent across all the ways issues are created, in order to avoid any confusion
- via the Jira create button
- via the JSM Customer portal
- via the Advanced Roadmap plans
- relates to
-
- Gathering Interest
- links to
[JSWSERVER-25111] Advanced Roadmap is not consistent with Jira and JSM in the way it handles the default "none" priority when issues are created from plans
| Labels | Original: Plan-Roadmap | New: Plan-Roadmap ril |
| Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 979607 ] |
| Component/s | Original: Plan [ 48691 ] | |
| Component/s | New: (Advanced Roadmaps) Plan - Roadmap [ 63498 ] | |
| Key | Original: JPOSERVER-9505 | New: JSWSERVER-25111 |
| Project | Original: Advanced Roadmaps [ 16510 ] | New: Jira Software Server and Data Center [ 12200 ] |
| Labels | New: Plan-Roadmap |
| Summary | Original: Better handle the default "none" priority when issues are created from a Roadmap plan | New: Advanced Roadmap is not consistent with Jira and JSM in the way it handles the default "none" priority when issues are created from plans |
| Link | New: This issue relates to JRASERVER-70654 [ JRASERVER-70654 ] |
| Description |
Original:
h3. Issue
When a Jira issue is created from a Roadmap plan in the case where the default priority is set to "none" in the priority scheme, the way the issue is created is not consistent with how the issue is created via the normal Jira *Create* button, or via the JSM Customer Portal: - in the case of the Jira *Create* button and the JSM Customer Portal, the issue will be created with a priority set (the priority listed in the middle of the priority scheme will be automatically chosen). -> This behavior is described in JRASERVER-70654 !IssueCreated_FromCreateButton.png|thumbnail! - however, in the case of Roadmap plans, the issue will be created without a priority !IssueCreated_FromRoadmapPlan.png|thumbnail! h3. Suggestion Make sure that the way the "none" default priority is handled is consistent across all the ways issues are created, in order to avoid any confusion - via the Jira *create* button - via the JSM Customer portal - via the Advanced Roadmap plans |
New:
h3. Issue
When a Jira issue is created from a Roadmap plan in the case where the default priority is set to "none" in the priority scheme, the way the issue is created is not consistent with how the issue is created via the normal Jira *Create* button, or via the JSM Customer Portal: - in the case of the Jira *Create* button and the JSM Customer Portal, the issue will be created with a priority set (the priority listed in the middle of the priority scheme will be automatically chosen). -> This behavior is described in JRASERVER-70654 !IssueCreated_FromCreateButton.png|thumbnail! - however, in the case of Roadmap plans, the issue will be created without a priority !IssueCreated_FromRoadmapPlan.png|thumbnail! (i) This is what the Priority scheme will look like, if "none" is selected: !PriorityScheme.png|thumbnail! h3. Suggestion Make sure that the way the "none" default priority is handled is consistent across all the ways issues are created, in order to avoid any confusion - via the Jira *create* button - via the JSM Customer portal - via the Advanced Roadmap plans |
| Description |
Original:
h3. Issue
When a Jira issue is created from a Roadmap plan in the case where the default priority is set to "none" in the priority scheme, the way the issue is created is not consistent with how the issue is created via the normal Jira *Create* button, or via the JSM Customer Portal: - in the case of the Jira *Create* button and the JSM Customer Portal, the issue will be created with a priority set (the priority listed in the middle of the priority scheme will be automatically chosen). -> This behavior is described in JRASERVER-70654 !IssueCreated_FromCreateButton.png|thumbnail! - however, in the case of Roadmap plans, the issue will be created without a priority h3. Suggestion Make sure that the way the "none" default priority is handled is consistent across all the ways issues are created, in order to avoid any confusion - via the Jira *create* button - via the JSM Customer portal - via the Advanced Roadmap plans |
New:
h3. Issue
When a Jira issue is created from a Roadmap plan in the case where the default priority is set to "none" in the priority scheme, the way the issue is created is not consistent with how the issue is created via the normal Jira *Create* button, or via the JSM Customer Portal: - in the case of the Jira *Create* button and the JSM Customer Portal, the issue will be created with a priority set (the priority listed in the middle of the priority scheme will be automatically chosen). -> This behavior is described in JRASERVER-70654 !IssueCreated_FromCreateButton.png|thumbnail! - however, in the case of Roadmap plans, the issue will be created without a priority !IssueCreated_FromRoadmapPlan.png|thumbnail! h3. Suggestion Make sure that the way the "none" default priority is handled is consistent across all the ways issues are created, in order to avoid any confusion - via the Jira *create* button - via the JSM Customer portal - via the Advanced Roadmap plans |
| Description |
Original:
h3. Issue
When a Jira issue is created from a Roadmap plan in the case where the default priority is set to "none" in the priority scheme, the way the issue is created is not consistent with how the issue is created via the normal Jira *Create* button, or via the JSM Customer Portal: - in the case of the Jira *Create* button and the JSM Customer Portal, the issue will be created with a priority set (the priority listed in the middle of the priority scheme will be automatically chosen). -> This behavior is described in JRASERVER-70654 - however, in the case of Roadmap plans, the issue will be created without a priority h3. Suggestion Make sure that the way the "none" default priority is handled is consistent across all the ways issues are created, in order to avoid any confusion - via the Jira *create* button - via the JSM Customer portal - via the Advanced Roadmap plans |
New:
h3. Issue
When a Jira issue is created from a Roadmap plan in the case where the default priority is set to "none" in the priority scheme, the way the issue is created is not consistent with how the issue is created via the normal Jira *Create* button, or via the JSM Customer Portal: - in the case of the Jira *Create* button and the JSM Customer Portal, the issue will be created with a priority set (the priority listed in the middle of the priority scheme will be automatically chosen). -> This behavior is described in JRASERVER-70654 !IssueCreated_FromCreateButton.png|thumbnail! - however, in the case of Roadmap plans, the issue will be created without a priority h3. Suggestion Make sure that the way the "none" default priority is handled is consistent across all the ways issues are created, in order to avoid any confusion - via the Jira *create* button - via the JSM Customer portal - via the Advanced Roadmap plans |