-
Bug
-
Resolution: Not a bug
-
High
-
None
-
5
-
Severity 3 - Minor
-
3
-
Update on December 30, 2022
Hello Jira community,
On Jira Cloud, the last Issue Type used on the Create issue screen is maintained across browser sessions. This isn't a bug but expected functionality. For additional flexibility in configuring the default Issue Type, you can vote and/or JRACLOUD-74771.
Thank you,
Arbaaz Gowher
Product Manager, Jira Platform
Issue Summary
According to the KB articles below, JIRA should reset the issue type to the default one when creating ticket in a new user session. However JIRA will still remember the last issue type when creating ticket in the same project after user has opened a new session.
- https://confluence.atlassian.com/jirakb/how-to-change-the-default-issue-type-displayed-at-the-create-issue-screen-707986896.html
- https://confluence.atlassian.com/jirakb/default-issue-type-when-create-an-issue-301662415.html
Steps to Reproduce
- Set a default issue type in project settings.
- Create a ticket with an issue type that is different from the default one.
- Logout JIRA and login again or open JIRA in another browser.
- Click Create button to create a ticket in the same project.
Expected Results
In the issue creation form the issue type should be reset to the default one.
Actual Results
In the issue creation form the issue type remains the one that has been selected in step 2.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- relates to
-
-
- Gathering Impact
-
-
JRACLOUD-74771 Default issue type additional option to not use session (last used)
- Gathering Interest
- mentioned in
-
Page Failed to load
[JRACLOUD-79915] Issue type is not reset to the default one when creating ticket in a new session
| Remote Link | New: This issue links to "Page (Confluence)" [ 805542 ] |
| Link | New: This issue relates to JRACLOUD-74771 [ JRACLOUD-74771 ] |
| Resolution | New: Not a bug [ 12 ] | |
| Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
| Description |
Original:
Hello Jira community,
On Jira Cloud, the last Issue Type used on the Create issue screen is maintained across browser sessions. This isn't a bug but expected functionality. For additional flexibility in configuring the default Issue Type, you can vote and/or JRACLOUD-74771. Thank you, Arbaaz Gowher Product Manager, Jira Platform h3. Issue Summary According to the KB articles below, JIRA should reset the issue type to the default one when creating ticket in a new user session. However JIRA will still remember the last issue type when creating ticket in the same project after user has opened a new session. * [https://confluence.atlassian.com/jirakb/how-to-change-the-default-issue-type-displayed-at-the-create-issue-screen-707986896.html] * [https://confluence.atlassian.com/jirakb/default-issue-type-when-create-an-issue-301662415.html] h3. Steps to Reproduce # Set a default issue type in project settings. # Create a ticket with an issue type that is different from the default one. # Logout JIRA and login again or open JIRA in another browser. # Click *Create* button to create a ticket in the same project. h3. Expected Results In the issue creation form the issue type should be reset to the default one. h3. Actual Results In the issue creation form the issue type remains the one that has been selected in step 2. h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
New:
{panel:title=Update on December 30, 2022}
Hello Jira community, On Jira Cloud, the last Issue Type used on the Create issue screen is maintained across browser sessions. This isn't a bug but expected functionality. For additional flexibility in configuring the default Issue Type, you can vote and/or JRACLOUD-74771. Thank you, Arbaaz Gowher Product Manager, Jira Platform {panel} h3. Issue Summary According to the KB articles below, JIRA should reset the issue type to the default one when creating ticket in a new user session. However JIRA will still remember the last issue type when creating ticket in the same project after user has opened a new session. * [https://confluence.atlassian.com/jirakb/how-to-change-the-default-issue-type-displayed-at-the-create-issue-screen-707986896.html] * [https://confluence.atlassian.com/jirakb/default-issue-type-when-create-an-issue-301662415.html] h3. Steps to Reproduce # Set a default issue type in project settings. # Create a ticket with an issue type that is different from the default one. # Logout JIRA and login again or open JIRA in another browser. # Click *Create* button to create a ticket in the same project. h3. Expected Results In the issue creation form the issue type should be reset to the default one. h3. Actual Results In the issue creation form the issue type remains the one that has been selected in step 2. h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
| Description |
Original:
{panel:title=Update on December 30, 2022}
{panel} h3. Issue Summary According to the KB articles below, JIRA should reset the issue type to the default one when creating ticket in a new user session. However JIRA will still remember the last issue type when creating ticket in the same project after user has opened a new session. * [https://confluence.atlassian.com/jirakb/how-to-change-the-default-issue-type-displayed-at-the-create-issue-screen-707986896.html] * [https://confluence.atlassian.com/jirakb/default-issue-type-when-create-an-issue-301662415.html] h3. Steps to Reproduce # Set a default issue type in project settings. # Create a ticket with an issue type that is different from the default one. # Logout JIRA and login again or open JIRA in another browser. # Click *Create* button to create a ticket in the same project. h3. Expected Results In the issue creation form the issue type should be reset to the default one. h3. Actual Results In the issue creation form the issue type remains the one that has been selected in step 2. h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
New:
Hello Jira community,
On Jira Cloud, the last Issue Type used on the Create issue screen is maintained across browser sessions. This isn't a bug but expected functionality. For additional flexibility in configuring the default Issue Type, you can vote and/or JRACLOUD-74771. Thank you, Arbaaz Gowher Product Manager, Jira Platform h3. Issue Summary According to the KB articles below, JIRA should reset the issue type to the default one when creating ticket in a new user session. However JIRA will still remember the last issue type when creating ticket in the same project after user has opened a new session. * [https://confluence.atlassian.com/jirakb/how-to-change-the-default-issue-type-displayed-at-the-create-issue-screen-707986896.html] * [https://confluence.atlassian.com/jirakb/default-issue-type-when-create-an-issue-301662415.html] h3. Steps to Reproduce # Set a default issue type in project settings. # Create a ticket with an issue type that is different from the default one. # Logout JIRA and login again or open JIRA in another browser. # Click *Create* button to create a ticket in the same project. h3. Expected Results In the issue creation form the issue type should be reset to the default one. h3. Actual Results In the issue creation form the issue type remains the one that has been selected in step 2. h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
| Description |
Original:
h3. Issue Summary
According to the KB articles below, JIRA should reset the issue type to the default one when creating ticket in a new user session. However JIRA will still remember the last issue type when creating ticket in the same project after user has opened a new session. * https://confluence.atlassian.com/jirakb/how-to-change-the-default-issue-type-displayed-at-the-create-issue-screen-707986896.html * https://confluence.atlassian.com/jirakb/default-issue-type-when-create-an-issue-301662415.html h3. Steps to Reproduce # Set a default issue type in project settings. # Create a ticket with an issue type that is different from the default one. # Logout JIRA and login again or open JIRA in another browser. # Click *Create* button to create a ticket in the same project. h3. Expected Results In the issue creation form the issue type should be reset to the default one. h3. Actual Results In the issue creation form the issue type remains the one that has been selected in step 2. h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
New:
{panel:title=Update on December 30, 2022}
{panel} h3. Issue Summary According to the KB articles below, JIRA should reset the issue type to the default one when creating ticket in a new user session. However JIRA will still remember the last issue type when creating ticket in the same project after user has opened a new session. * [https://confluence.atlassian.com/jirakb/how-to-change-the-default-issue-type-displayed-at-the-create-issue-screen-707986896.html] * [https://confluence.atlassian.com/jirakb/default-issue-type-when-create-an-issue-301662415.html] h3. Steps to Reproduce # Set a default issue type in project settings. # Create a ticket with an issue type that is different from the default one. # Logout JIRA and login again or open JIRA in another browser. # Click *Create* button to create a ticket in the same project. h3. Expected Results In the issue creation form the issue type should be reset to the default one. h3. Actual Results In the issue creation form the issue type remains the one that has been selected in step 2. h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
| Assignee | New: Arbaaz Gowher [ 7645729f7e9f ] |
| UIS | Original: 2 | New: 3 |
| Component/s | Original: Global Administration - Fields, Issue Types, Screens and Other [ 66292 ] |
| Support reference count | Original: 4 | New: 5 |