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

Default issue type additional option to not use session (last used)

    • 138
    • 84
    • 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.

      Problem

      The "Default issue type" dropdown is only honoured when the user has not previously selected an issue type, so only works once after logging in.

      It'd be useful to have a hard default that is always used with every new issue created.

      The current functionality should be retained and be the default configuration, to avoid backwards compatibility problems and to avoid making one group happy at a loss to another.

      Suggested solution

      1. Add a new checkbox underneath the "Default issue type" dropdown with the label: "Re-use the previously selected issue type"
      2. New checkbox checked by default to retain current functionality and BC

      Outcome

      • When checkbox is checked (and previously chosen issue type exists)
        • The user's previously chosen issue type will be used
        • Current functionality retained
        • Backwards compatible
      • When checkbox not checked (or previously chosen issue type doesn't exist)
        • The "Default issue type" will be used
        • New functionality gained for users wanting it
        • The "Default issue type" wording is now a bit more accurate/meaningful

       

          Form Name

            [JRACLOUD-74771] Default issue type additional option to not use session (last used)

            David Erickson added a comment - - edited

            The suggestion makes the most sense to me, however I could see using the "last used" Issue Type on the "Create Another" feature.  "Create Another" seems like the sequence that would be used most in brainstorming, testing, or elaboration sessions and that's where you want to rapid-fire a lot of issues.  Using the generic "Create" button on the form should respect the project settings as described above.

            The current behavior results in a lot of issues reported as bugs instead of improvements or vice versa, based on whatever that user did the last usage.  The users enter these issues as they come across them either by usage problems (bugs) or inspiration (improvements).  Erroneous entries impact our triage effectiveness and responsiveness.  In our case, we would set the default to "None" but make the field required.  The user would have to at least choose between these two options, and we may re-categorize upon triage.

            David Erickson added a comment - - edited The suggestion makes the most sense to me, however I could see using the "last used" Issue Type on the "Create Another" feature.  "Create Another" seems like the sequence that would be used most in brainstorming, testing, or elaboration sessions and that's where you want to rapid-fire a lot of issues.  Using the generic "Create" button on the form should respect the project settings as described above. The current behavior results in a lot of issues reported as bugs instead of improvements or vice versa, based on whatever that user did the last usage.  The users enter these issues as they come across them either by usage problems (bugs) or inspiration (improvements).  Erroneous entries impact our triage effectiveness and responsiveness.  In our case, we would set the default to "None" but make the field required.  The user would have to at least choose between these two options, and we may re-categorize upon triage.

            +1

            Ludivine Meys added a comment - +1

            +1 my users constantly complain that they have to change the issue type. Story should always be the default, independently from what was created last.  Or at lest make this configurable in the project... 

            Finn Rakow added a comment - +1 my users constantly complain that they have to change the issue type. Story should always be the default, independently from what was created last.  Or at lest make this configurable in the project... 

            +1 This would reduce issue type errors.

            Marie Luquet added a comment - +1 This would reduce issue type errors.

            Cody added a comment -

            Cody added a comment - https://getsupport.atlassian.com/browse/PCS-322745

            Inder Dhir added a comment -

            +1

            Inder Dhir added a comment - +1

            Why not just sort out the Issue Types on the drop-down as it's done for Custom Fields with drop-down lists? This could be associated to the projects Issue Type Scheme.

            Sérgio Nogueira added a comment - Why not just sort out the Issue Types on the drop-down as it's done for Custom Fields with drop-down lists? This could be associated to the projects Issue Type Scheme.

            Isai Navarro added a comment - https://getsupport.atlassian.com/browse/JST-1018316

            +1

            What's the sense of this Setting if it only applies once when the user creates the first ticket.

            Default issue type should be applied to the creation screen for all attempts of creation.

            Raman Bandarenka added a comment - +1 What's the sense of this Setting if it only applies once when the user creates the first ticket. Default issue type should be applied to the creation screen for all attempts of creation.

            bugcrowd. added a comment -

            hoop

             

            bugcrowd. added a comment - hoop  

              7645729f7e9f Arbaaz Gowher (Inactive)
              ccf376c73a87 Greg Sanderson
              Votes:
              170 Vote for this issue
              Watchers:
              112 Start watching this issue

                Created:
                Updated: