Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-40898

Default Issue Type - value from Issue Type Scheme is not used.

XMLWordPrintable

      Summary:
      Default Issue Type parameter within the Issue Type Scheme, is being ignored for users who have created an issue in the same session or users who are switching projects.

      Steps to Reproduce:

      1. Create two projects.
      2. Create two new Issue Type schemes and associate one with each project.
      3. Set the Default Issue Type to a unique setting for each Issue Type Scheme (example: scheme 1: Task scheme 2: New Feature)
      4. Start browser in incognito mode
      5. Log in, and create an issue on project 1
      6. You will see the defined Issue Type, change it.
      7. Create another issue within the same project

      Expected Results:
      Default Issue Type should be selected.

      Actual Results:
      The previously selected Issue Type is selected.

      Notes:
      This also happens when switching to a different project as per step 7.
      I found a related issue JRA-24439, here it states this is expected behaviour, but it also states that the correct scheme value should be picked up when changing projects, which it does not currently.

            [JRASERVER-40898] Default Issue Type - value from Issue Type Scheme is not used.

            Vicki Lea Tsang added a comment -

            I think most responses for this are actually being entered on to JRASERVER-30620 but the responses there show that this is generally viewed as a bug within Jira. Please reopen.

            Vicki Lea Tsang added a comment - I think most responses for this are actually being entered on to JRASERVER-30620 but the responses there show that this is generally viewed as a bug within Jira. Please reopen.

            Colin Higbie added a comment -

            This is clearly a bug. If I set a default behavior value for the drop-down and it has some value other than the default before the user changes it, that's a bug.

            Colin Higbie added a comment - This is clearly a bug. If I set a default behavior value for the drop-down and it has some value other than the default before the user changes it, that's a bug.

            Michael I. added a comment -

            Dear Atlassian Team,
            Could you please clarify, why do this behavior is "Not a bug"?

            Michael I. added a comment - Dear Atlassian Team, Could you please clarify, why do this behavior is "Not a bug"?

              Unassigned Unassigned
              ilabras Ibrahim (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: