Filter/Report on LinkedIssues and their date

[Jennifer Hart]

I am very new to Jira so I apologize if this seems very basic. I have a filter where I include the LinkedIssue ID. I want to also include the Forecasted Go-Live date of the LinkedIssue (not just of the issue itself) How can I accomplish this?

[Hannes Obweger - JXL for Jira]

Hi @Jennifer Hart

welcome to the community!

To see the go-live date of your linked issues (or any field of your linked issues), you would have to include these issues into your search result, as separate line items. This, unfortunately, is a little trickier in Jira, as Jira doesn't natively support joins or subqueries (in database query lingo). 

A few ways forward:

• If it's a one-off thing, you could first query your "main" issues (the one that are returned by your JQL query), and then use the issue keys in an OR issueLink in (<main-issue-key-1>, <main-issue-key-2>, ...) clause. Note that this will give you just a flat list of issues, without a meaningful order. You may be able to tweak the result using ORDER BY clauses, but I'm not sure you'll manage to consistently keep the related issues together. 

If you want to run your query dynamically, without stitching things together as described above, you'll need extra tooling:

• There's a number of apps in the Atlassian Marketplace that extend JQL by additional functions, including issue-link related ones. The problem here is that they still will only give you a flat list of issues, as described above.
• Alternatively, you may want to try one of the more hierarchy-focused apps from the Marketplace. These apps typically have their own ways of figuring out parent/child relationships between issues, and provide more powerful ways of searching through issue hierarchies. I myself work on such an app, in which your use case would be easy to solve - I'll provide more details below.

[Hannes Obweger - JXL for Jira]

Just to expand on the last point, this is how this would look in the app that my team and I are working on, JXL for Jira:

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a number of advanced features, including support for (configurable) issue hierarchies. These issue hierarchies can be based on Jira's built-in parent/child relationships (like task/sub-task) and/or based on issue links. With this, you can build a view like the one above in just a couple of clicks.

Any questions just let me know,

Best,

Hannes

[Jennifer Hart]

As much as I would love to use third party tools, it's not anything I have authorization (or money) to do, so I'd probably want to go with your first suggestion. How would I accomplish this part " and then use the issue keys in an OR issueLink in (<main-issue-key-1>, <main-issue-key-2>, ...) clause" Would it be part of the same JSQL query?

[Hannes Obweger - JXL for Jira]

Hi @Jennifer Hart,

no worries - yes, this would be part of the same JQL query. So, if you first do -

project = SSU AND issuetype = "Client Software Upgrade" AND status in (Discovery, "Go-Live Support", New, Pending, Planning, Scheduled) AND assignee in (EMPTY)

- then grab the issue keys of the result, and add them to the query like so -

(project = SSU AND issuetype = "Client Software Upgrade" AND status in (Discovery, "Go-Live Support", New, Pending, Planning, Scheduled) AND assignee in (EMPTY)) OR issueLink in (<main-issue-key-1>, <main-issue-key-2>, ...)

 - then you should get all relevant issues. Does that work?

The challenge then is to get them into a meaningful order. As said above, you'll likely want to play around with ORDER BY clauses, but I'm not sure how and if you'd achieve the expected outcome.

Best,

Hannes

[Jennifer Hart]

Looking at the logic I don't think it's what I'm looking for. What you have does seem like like it is including the date field in the query. I don't need to look for issues within a certain issuelink-every issue I have will have a corresponding linkedissue and each wil have a forecasted date that I'd like to see next to each other to do a visual compare. I hope that makes sense.

[Hannes Obweger - JXL for Jira]

@Jennifer Hart

every issue I have will have a corresponding linkedissue and each wil have a forecasted date that I'd like to see next to each other to do a visual compare

Yep, I think I get it. The problem is that this won't be possible; if you retrieve an issue via JQL, you can't just see another issue's field(s).

To see the other issue's field(s), the other issue must also be in your JQL filter result, as it's own line item. 

That's what I've been trying to achieve here. Does this make sense?

[Bill Sheboy]

Hi @Jennifer Hart -- Welcome to the Atlassian Community!

Would you please post the JQL you are trying to use?

And...are you trying to filter on that other field or just display the values for the issues found?

Kind regards,
Bill

[Jennifer Hart]

Hi @Bill Sheboy 

This is what I have so far for the JSQL. Basically, I'd like to add another column that would be the Forecasted Go-Live date of the Linked issue.

project = SSU AND issuetype = "Client Software Upgrade" AND status in (Discovery, "Go-Live Support", New, Pending, Planning, Scheduled) AND assignee in (EMPTY) order by created DESC

[Bill Sheboy]

At the right side of that view, above the displayed issues, there is a Columns drop-down list to select which fields are displayed for the search.

[Jennifer Hart]

You are right that there are additional columns to add, but there is not the column I am looking for.

[Bill Sheboy]

Is that a custom field your team has added or is it from a marketplace addon?

[Jennifer Hart]

No it's not a custom field and we don't use any add-ons. It's just a default field that part of the linked issue.

[Bill Sheboy]

Is that a field from Advanced Roadmap?  I am not using that tool and so cannot check that.

Would you please show an image where you see that field in the UI?

If it is a calculated field from Advanced Roadmaps, I would also expect it cannot be reported upon with an issue search.

[Jennifer Hart]

It isn't a calculated field. It's just one of the date fields in the linkedissue. 

[Bill Sheboy]

As you note it is an out-of-the-box field and not calculated, I am unclear why it would not be reportable with an issue search.  I did a quick search of the public backlog and do not see this symptom noted.

You are on a premium license, and so I suggest working with your Jira Site Admin to submit a ticket to Atlassian Support here: https://support.atlassian.com/contact/#/

When you hear back from them, please post what you learn to benefit the community.  Thanks!