-
Suggestion
-
Resolution: Duplicate
-
None
-
None
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Problem Definition
Based on the information located on this bug : https://jira.atlassian.com/browse/JRA-30620
Specifically: Once a user has created an issue in a project in the current session, JIRA retains the issue type from the previous issue any time the user creates a new issue in the same project. This is intended to make it easier for users to quickly create issues, such as when a software developer is creating a number of stories for a sprint or a QA engineer is filing bugs.
Requesting that this behavior has a toggle so that we can
Suggested Solution
Requesting that this behavior has a toggle so that we can choose the behavior of the default issue type to always use the default specified and not retain the last used.
Workaround
(Optional)
- is duplicated by
-
JRACLOUD-74771 Default issue type additional option to not use session (last used)
- Gathering Interest
- is related to
-
JRASERVER-62990 Default issue type behavior options
- Closed
[JRACLOUD-62990] Default issue type behavior options
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
Link | New: This issue is duplicated by JRACLOUD-74771 [ JRACLOUD-74771 ] |
Workflow | Original: JAC Suggestion Workflow [ 3142041 ] | New: JAC Suggestion Workflow 3 [ 3637265 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2336969 ] | New: JAC Suggestion Workflow [ 3142041 ] |
Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 2101657 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2336969 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2064042 ] | New: JIRA Bug Workflow w Kanban v6 [ 2101657 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 1835701 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2064042 ] |
Description |
Original:
h3. Problem Definition Based on the information located on this bug : https://jira.atlassian.com/browse/JRA-30620 Specifically: Once a user has created an issue in a project in the current session, JIRA retains the issue type from the previous issue any time the user creates a new issue in the same project. This is intended to make it easier for users to quickly create issues, such as when a software developer is creating a number of stories for a sprint or a QA engineer is filing bugs. Requesting that this behavior has a toggle so that we can h3. Suggested Solution Requesting that this behavior has a toggle so that we can choose the behavior of the default issue type to always use the default specified and not retain the last used. h3. Workaround (Optional) |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Cloud*. Using *JIRA Server*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRASERVER-62990]. {panel} h3. Problem Definition Based on the information located on this bug : https://jira.atlassian.com/browse/JRA-30620 Specifically: Once a user has created an issue in a project in the current session, JIRA retains the issue type from the previous issue any time the user creates a new issue in the same project. This is intended to make it easier for users to quickly create issues, such as when a software developer is creating a number of stories for a sprint or a QA engineer is filing bugs. Requesting that this behavior has a toggle so that we can h3. Suggested Solution Requesting that this behavior has a toggle so that we can choose the behavior of the default issue type to always use the default specified and not retain the last used. h3. Workaround (Optional) |
Link |
New:
This issue is related to |
Project Import | New: Sat Apr 01 19:36:47 UTC 2017 [ 1491075407146 ] |