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

Epic Link on the issue navigator is not sorted base on the Epic key

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • None

      Steps to produce:

      1. Create GH board with multiple Epics.
      2. Add as many issues to these Epics.
      3. Go to the issue navigator, add the Epic Link column to the issue navigator and sort the issues base on the Epic Link.

      Actual Results
      Issues are randomly sorted whereby there is no an exact pattern to follow (nor the Epic key or link Id from the DB)

      Expect Results
      Once the used order the issues base on the Epic Link, issues should be sorted base on the Epic Key.

            [JSWCLOUD-8515] Epic Link on the issue navigator is not sorted base on the Epic key

            ITSupport added a comment -

            Hello,

            we are also affected with this Issue. We hope this is provided very soon. This should be available as part of basic ordering functionality.

            Please, adjust higher priority issue!

            Thank you,

            ITSupport added a comment - Hello, we are also affected with this Issue. We hope this is provided very soon. This should be available as part of basic ordering functionality. Please, adjust higher priority issue! Thank you,

            Michael Tokar added a comment -

            Disregard. I must have been looking at the issue key from my email notification which was prior to the move.

            Michael Tokar added a comment - Disregard. I must have been looking at the issue key from my email notification which was prior to the move.

            Eric Dalgliesh added a comment -

            This is the issue in the GH project - I did a project move! Should I copy it somewhere else?

            Eric Dalgliesh added a comment - This is the issue in the GH project - I did a project move! Should I copy it somewhere else?

            Michael Tokar added a comment -

            edalgliesh where is the issue in GH project?

            Michael Tokar added a comment - edalgliesh where is the issue in GH project?

            Eric Dalgliesh added a comment -

            Moved to greenhopper project as I suspect the change that needs to be made lives in in the searcher for Epics.

            Eric Dalgliesh added a comment - Moved to greenhopper project as I suspect the change that needs to be made lives in in the searcher for Epics.

            Maarten Cautreels added a comment -

            For the record: we are on version 6.0-OD-09-5 on our OnDemand instance.

            Maarten Cautreels added a comment - For the record: we are on version 6.0-OD-09-5 on our OnDemand instance.

            Eric Dalgliesh added a comment -

            mtokar any idea if this is already fixed in JIRA 6.0? Also is it likely to be in JIRA or GH we'll need to make a fix?

            Eric Dalgliesh added a comment - mtokar any idea if this is already fixed in JIRA 6.0? Also is it likely to be in JIRA or GH we'll need to make a fix?

              Unassigned Unassigned
              oalsafi OmarA
              Affected customers:
              12 This affects my team
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: