Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-10472

"Create Issue" Sets Rank Randomly

XMLWordPrintable

      Creating issues in JIRA sets ranking inconsistently.

      Steps to Replicate the Problem:

      • Creating an Issue from a view other than the Planning Board (e.g. from the dashboard) causes the issue to appear at the bottom of the Planning View.
      • When creating it from the Planning View, the new ticket will automatically appear underneath whichever ticket is currently selected.
      • If no ticket is selected in the Planning View and a new ticket is added, that ticket will appear at the TOP of the backlog. To reproduce, just manually remove the selectedIssue=XXX query string parameter from the Planning View URL and try to create a new ticket.

      Expected Behavior:

      Creating a new issue should put it to the bottom of the backlog at all times, to prevent accidentally giving the issue a priority.

      Ref.: https://answers.atlassian.com/questions/198381/configuring-new-issue-planning-board-position

        1. Screen.PNG
          Screen.PNG
          12 kB

          Form Name

            [JSWSERVER-10472] "Create Issue" Sets Rank Randomly

            Bugfix Automation Bot made changes -
            Minimum Version New: 6.02
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2850527 ] New: JAC Bug Workflow v3 [ 2938280 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Symptom Severity Original: Minor [ 14432 ] New: Severity 3 - Minor [ 15832 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2545250 ] New: JAC Bug Workflow v2 [ 2850527 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1552131 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2545250 ]
            Marek Broda (Inactive) made changes -
            Resolution New: Not a bug [ 12 ]
            Status Original: Needs Verification [ 10004 ] New: Resolved [ 5 ]

            Marek Broda (Inactive) added a comment -

            This ticket will be closed, as it does not seem to be a bug. A corresponding Suggestion ticket has been created here: JSW-10846. If you have any additional comments and/or suggestions, please add them to that ticket.

             

            Kind regards,

            The JIRA Software Team

            Marek Broda (Inactive) added a comment - This ticket will be closed, as it does not seem to be a bug. A corresponding Suggestion ticket has been created here:  JSW-10846 . If you have any additional comments and/or suggestions, please add them to that ticket.   Kind regards, The JIRA Software Team
            Hoang Dong (Inactive) made changes -
            Comment [ A comment with security level 'atlassian-staff' was removed. ]
            Hoang Dong (Inactive) made changes -
            Status Original: Open [ 1 ] New: Needs Verification [ 10004 ]
            Hoang Dong (Inactive) made changes -
            Status Original: Verified [ 10005 ] New: Open [ 1 ]

              Unassigned Unassigned
              6685795f6817 Fabian Ehrentraud
              Affected customers:
              16 This affects my team
              Watchers:
              23 Start watching this issue

                Created:
                Updated:
                Resolved: