Uploaded image for project: 'Jira Software Server and Data Center'
  1. Jira Software Server and Data Center
  2. JSWSERVER-11749

Inline issue creation should use the default type from the Issue Type Scheme

    XMLWordPrintable

    Details

    • Feedback Policy:
      We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Description

      current behaviour
      1. Initially, the inline issue creation in Agile board backlog pre-selects the issue type based on the alphabetical order of available types.
      2. After a user changes the issue type and creates an issue with it, the new default type will be cached in their browser.
      3. The new default type is retained until an issue with a different type is created, or the user clears their browsing data.

      Example: in the applicable Issue Type Scheme, "Task" is the default type, but "Bug" is higher in the alphabetical order. In the inline issue creation, "Bug" will be the default issue type at first. If a user changes it and creates a "Task" though, it will be the default type from then on - until an issue of another type is created.

      suggestion

      Initially, the default type from the applicable Issue Type Scheme should be selected in inline issue creation. Afterwards, the type can be determined by previous usage the way it is now.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              dwierzbicka Dobroslawa Wierzbicka (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: