Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-62990

Default issue type behavior options

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • None

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      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)

          Form Name

            [JRACLOUD-62990] Default issue type behavior options

            Belto added a comment -

            Dear Customers,

            After comparing this bug request against the known report JRACLOUD-74771 we realized that both are addressing the same scenario.

            Since we consider JRACLOUD-74771 the main point of entry for this scenario, we will be closing this request now and will ask you to cast your votes in the original request so we can measure the impact and interest more accurately.

            Cheers,

            Belto
            ATLASSIAN | Cloud Support Engineer | Amsterdam

            Belto added a comment - Dear Customers, After comparing this bug request against the known report JRACLOUD-74771 we realized that both are addressing the same scenario. Since we consider JRACLOUD-74771 the main point of entry for this scenario, we will be closing this request now and will ask you to cast your votes in the original request so we can measure the impact and interest more accurately. Cheers, Belto ATLASSIAN | Cloud Support Engineer | Amsterdam

              Unassigned Unassigned
              b2a4ae24bc79 Trudy Claspill
              Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: