Uploaded image for project: 'Jira Software Cloud'
  1. Jira Software Cloud
  2. JSWCLOUD-26233

Inconsistent Behavior when Creating Issues via Backlog "+ Create issue" button.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Low
    • Epic renaming
    • None

    Description

      Issue Summary

      On the backlog page, when creating issues via the "+ Create issue" button at the bottom of a planned sprint or on the backlog section, it's not possible to change the Epic on the "Parent" field.

      Steps to Reproduce

      The problems seem to only happen when specific conditions are met:

      1. You must be on the backlog a board (Scrum/Kanban)
      2. The issue creation modal should trigger when clicking the "+ Create issue" button to quickly create issues:
        • The modal will trigger when there are fields other than Summary that are required to create issues, or
        • When the board's filter refers to a field that no longer exists (known bug)
      3. When you click on "+ Create issue", the modal will appear where Summary and all other required fields must be provided. On the modal, the "Parent" field will be already filled with the last Epic that has been selected on the Epic filter of the board. This is the expected behavior when the create issue modal doesn't appear, as it should create the new issue inside the last selected Epic
      4. For cases when the Create Issue modal does appear, and you try to change, on the "Parent" field, the Epic to any other, changes won't be kept. The last Selected Epic will be used always.

      Expected Results

      On the Issue creation modal, If the Epic is changed on the "Parent" field, the new issue should be created under the newly selected Epic.

      Actual Results

      On the Issue creation modal, If the Epic is manually changed on the "Parent" field, the issue is still created on the Epic that was on the Field before the manual change. This is the last Epic that has been selected on the Epic filter of the board.

      Workaround

      The workaround is to manually update the "Parent" field after the issue is created.

      Attachments

        Issue Links

          Activity

            People

              2e6e6483d7d1 Konstantin Kulishenkov
              d80b1397fd0f Guilherme Barbosa Lima
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: