How to track status of multiple projects which have inter-dependency through Jira Software

Question

How to track status of multiple projects which have inter-dependency through Jira Software ?

Our project team is working on a complex product development which involves multiple teams working on different interdependent modules. We have separate Jira projects for these teams but a common backlog. How can a MD or CTO track the progress of the product from a bird's eye view in Jira. We have been maintaining loads of complex excel sheets to achieve this. Would be nice if we could track all this using Jira Software.

Carlos Garcia Navarro · Answer

Hi @abhishek_sharma03 , I'm glad to hear that you found a solution that made your customer happy, nice job! :-)

abhishek_sharma03 · Answer

Hey Guys, @Carlos Garcia Navarro @John Funk , My client is not interested to purchase Portfolio for Jira (it being too expensive for him). Hence i advised a stop-gap solution for him by introducing a custom field named - Program. I made it a multi-select field as one story could be a part of 2 programs as well. I made it a mandatory field to be selected in requirement issuetypes (story or tasks). Then created filters similar to  below -

Project in ("API Development", "Digital Campaigns") AND Program in (Program1) ORDER BY created DESC

for all the programs and displayed them through a pie chart. By this way the client was able to see the high level progress on his initiatives / program. But he won't be able to judge if the progress is on track or not basis the target date.

Carlos Garcia Navarro · Answer

Yeah, I understand. I'm not sure how to accomplish this with native Jira, I'd probably make a case that Advanced Roadmaps/Portfolio could save time and maintenance of the excel sheet solution, which in the end would result in a good ROI. That said, before I had access to Portfolio and Jira Align, I built my own Confluence page with a table that contained Jira filters where I included dependencies. For that though, you'd need something like Script Runner's issueFunction. This is the JQL I used then:

(issueFunction in linkedIssuesOf("issuekey=<issue_key>") and  (resolutiondate >= -7d OR status not in (Resolved, Closed)) order by updated DES

The first clause gave me the dependencies for a specific issue, while the second clause would remove the issues that were closed except for those that were resolved in the last 7 days, I wanted to keep those in the query result to make people aware of the cases that were recently resolved.