nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Sorting issues by value in linked issue

Nikita Tagner

Hello,

Problem description:

My team uses a project , Project A.

In Project A, some issues have epic links to other issues. Lets call one of the issues in Project A Issue A1.

Issue A1 has an epic link to Issue B1. Issue B1 is in Project B.

Issue B1 has an epic link to Issue C1. Issue C1 is in Project C.

Issue C1 has a value in the fix version field. This value is important to my team as it determines when we will work on Issue A1. What our team wants is to, when we do our planning, easily see which issues in Project A are to be prioritized.

A picture is attached below for clarity.

So far, I have tried to create a filter. I can successfully obtain all issues in Project A that fit my criteria using the query:

issueFunction in hasLinkType("Epic-Story Link") and project = "A" and summary ~ "B*"

This gives me a list such as:

Issue A1 in Project A (Fix version of Issue C1: w1)

Issue A2 in Project A (Fix version of Issue C2: w3)

Issue A3 in Project A (Fix version of Issue C3: w2)

My questions are:

Is it possible to sort the resulting list after my query by the fix version field in the C issues? So that the list mentioned above looks more like:
Issue A1 in Project A (Fix version of Issue C1: w1)
Issue A3 in Project A (Fix version of Issue C3: w2) Issue A2 in Project A (Fix version of Issue C2: w3)
Is there some other way of solving this problem?

Thank you in advance for your help and let me know if anything is unclear.

Accepted answers

Marc Minten (EVS)

Hi,

I understand correctly you have scriptrunner installed ?

I would rather add a scripted field to the issues in project A, and put(calculate in a script) the release dates of the linked issue in project C in that field (or null is no linked issue found).

Then you can easily sort on that scripted field.

All comments

Ismael Jimoh

Hi @Nikita Tagner

I doubt this because the fix version would still be in Issue C1 not issue A1. If you must, I would suggest:

Create a fix version from the source project based of the linked ticket .
Apply the fix version to the issue your team is working on.

This way you can set the same fix version to the issue.

If you currently query for fix version, JIRA would think you are querying fix version for the issue itself which I guess you have not set yet.

Hope this helps.

Regards.

Marc Minten (EVS)

Hi,

I understand correctly you have scriptrunner installed ?

I would rather add a scripted field to the issues in project A, and put(calculate in a script) the release dates of the linked issue in project C in that field (or null is no linked issue found).

Then you can easily sort on that scripted field.

Nikita Tagner

Thank you for your response.

I do not understand what you mean when you write "source project" and "linked ticket". Could you elaborate please?