-
Bug
-
Resolution: Fixed
-
Low
-
None
-
1
-
Severity 3 - Minor
-
Issue Summary
We document here how the default issue type setting is meant to work:
https://confluence.atlassian.com/jirakb/how-to-change-the-default-issue-type-displayed-at-the-create-issue-screen-when-a-user-creates-an-issue-for-the-first-time-in-a-specific-project-707986896.html
This entire setting seems to be meant to apply only to the first time a user logs in. Subsequently, when creating an issue, Jira Cloud will show the issue type selected by the user when they last created an issue. This behaviour has changed in the Enhanced backlog and board making the issue-create behaviour inconsistent. If you create an issue using the Create button in the top nav bar, it will continue to display the most recent issue type the user selected.
If, however, you create an issue by going to the backlog and clicking "+ Create issue" and the default issue type is set to None, the user story issue type is shown instead.
Steps to Reproduce
- Enable the Enhanced backlog
- In a company-managed project go to Project Settings > Issues > Types and select Actions > Edit issue types
- Make sure there is some non-None value in the "Default Issue Type" dropdown. I chose the issue type "Ask a question":
- Go back to the project's board. Click the Create button in the top nav bar. Observe that in the issue Create screen, the selected issue type matches the type of the issue you last created. Mine was "Story":
- Go to your backlog and click "+ Create issue". Observe that the issue type matches the one selected in the issue type scheme ("Ask a question"):
- Disable the enhance backlog and click "+ Create issue" again - observe that the issue type is "Story"
Side note: If you select "None" as the "Default Issue Type" in your Issue Type Scheme the backlog issue create defaults to Story.
Expected Results
Consistency in behaviour from all issue creation methods in terms of default issue type. When "Default Issue Type" has a value, all issue create methods should respect it. When "Default Issue Type" has no value, the issue type of the last issue created should be used.
Actual Results
Inconsistent in behaviour from the top-nav bar Create button and issue creation methods on the Enhanced board and backlog
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- is related to
-
JRACLOUD-74771 Default issue type additional option to not use session (last used)
- Gathering Interest
[JRACLOUD-87418] Inconsistent default issue type behaviour when Enhanced backlog is enabled
| Component/s | Original: Backlog (Company) - Inline Issue Create [ 62205 ] | |
| Component/s | New: Backlog (Company) - Inline Issue Create [ 77913 ] | |
| Key |
Original:
|
New:
|
| Project | Original: Jira Cloud [ 18511 ] | New: Jira Platform Cloud [ 18514 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Progress [ 3 ] | New: Closed [ 6 ] |
| Link | New: This issue is related to JRACLOUD-74771 [ JRACLOUD-74771 ] |
| Status | Original: Needs Triage [ 10030 ] | New: In Progress [ 3 ] |
| Status | Original: In Progress [ 3 ] | New: Needs Triage [ 10030 ] |
| Component/s | Original: Board (UIF) [ 73190 ] | |
| Component/s | Original: Backlog (UIF) [ 73191 ] | |
| Component/s | New: Backlog (Company) - Inline Issue Create [ 62205 ] |
| Assignee | New: Chris Hanson [ edd6b3399298 ] |
| Status | Original: Long Term Backlog [ 12073 ] | New: In Progress [ 3 ] |
| Description |
Original:
h3. Issue Summary
We document here how the default issue type setting is meant to work: https://confluence.atlassian.com/jirakb/how-to-change-the-default-issue-type-displayed-at-the-create-issue-screen-when-a-user-creates-an-issue-for-the-first-time-in-a-specific-project-707986896.html This entire setting seems to be meant to apply only to the first time a user logs in. Subsequently, when creating an issue, Jira Cloud will show the issue type selected by the user when they last created an issue. This behaviour has changed in the Enhanced backlog and board making the issue-create behaviour inconsistent. If you create an issue using the *Create* button in the top nav bar, it will continue to display the most recent issue type the user selected. If, however, you create an issue by going to the backlog and clicking "+ Create issue" and the default issue type is set to None, the user story issue type is shown instead. h3. Steps to Reproduce # Enable the Enhanced backlog # In a company-managed project go to Project Settings > Issues > Types and select Actions > Edit issue types # Make sure there is some non-None value in the "Default Issue Type" dropdown. I chose the issue type "Ask a question": !image-2023-11-01-13-07-54-081.png|thumbnail! # Go back to the project's board. Click the Create button in the top nav bar. Observe that in the issue Create screen, the selected issue type matches the type of the issue you last created. Mine was "Story": !image-2023-11-01-13-10-13-026.png|thumbnail! # Go to your backlog and click "+ Create issue". Observe that the issue type matches the one selected in the issue type scheme ("Ask a question"): !image-2023-11-01-13-11-34-427.png|thumbnail! # Disable the enhance backlog and click "+ Create issue" again - observe that the issue type is "Story" Side note: If you select "None" as the "Default Issue Type" in your Issue Type Scheme the backlog issue create defaults to Story. h3. Expected Results Consistency in behaviour from all issue creation methods in terms of default issue type h3. Actual Results In consistent in behaviour from the top-nav bar Create button and issue creation methods on the Enhanced board and backlog h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
We document here how the default issue type setting is meant to work: [https://confluence.atlassian.com/jirakb/how-to-change-the-default-issue-type-displayed-at-the-create-issue-screen-when-a-user-creates-an-issue-for-the-first-time-in-a-specific-project-707986896.html] This entire setting seems to be meant to apply only to the first time a user logs in. Subsequently, when creating an issue, Jira Cloud will show the issue type selected by the user when they last created an issue. This behaviour has changed in the Enhanced backlog and board making the issue-create behaviour inconsistent. If you create an issue using the *Create* button in the top nav bar, it will continue to display the most recent issue type the user selected. If, however, you create an issue by going to the backlog and clicking "+ Create issue" and the default issue type is set to None, the user story issue type is shown instead. h3. Steps to Reproduce # Enable the Enhanced backlog # In a company-managed project go to Project Settings > Issues > Types and select Actions > Edit issue types # Make sure there is some non-None value in the "Default Issue Type" dropdown. I chose the issue type "Ask a question": !image-2023-11-01-13-07-54-081.png|thumbnail! # Go back to the project's board. Click the Create button in the top nav bar. Observe that in the issue Create screen, the selected issue type matches the type of the issue you last created. Mine was "Story": !image-2023-11-01-13-10-13-026.png|thumbnail! # Go to your backlog and click "+ Create issue". Observe that the issue type matches the one selected in the issue type scheme ("Ask a question"): !image-2023-11-01-13-11-34-427.png|thumbnail! # Disable the enhance backlog and click "+ Create issue" again - observe that the issue type is "Story" Side note: If you select "None" as the "Default Issue Type" in your Issue Type Scheme the backlog issue create defaults to Story. h3. Expected Results Consistency in behaviour from all issue creation methods in terms of default issue type. When "Default Issue Type" has a value, all issue create methods should respect it. When "Default Issue Type" has no value, the issue type of the last issue created should be used. h3. Actual Results Inconsistent in behaviour from the top-nav bar Create button and issue creation methods on the Enhanced board and backlog h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
| Status | Original: Needs Triage [ 10030 ] | New: Long Term Backlog [ 12073 ] |