How to show issues from multiple projects?

Question

Hi all,

Can someone advise me if this is even possible or any alternative.

We have Jira Service Management (Cloud) & Jira Software (Cloud).

Problem tickets are created in JSM project (say PRJ-JSM) and if there is a Bug identified for a Problem, then a linked Bug is created in JS (say PRJ-JS).

I want some way to list all bugs that are created in PRJ-JS, and are linked to project PRJ-JSM. This list / report will be run by an internal user who has access to both JSM & JS.

Regards,

Faisal

Daniel Ebers · Answer

Hi @Faisal

you would need to use JQL queries to get the information you are looking for in a listed format.

Per coincidence the very same day you asked the question there has been a similar question which was perfectly answered by Trudy:
https://community.atlassian.com/t5/Jira-Software-questions/Need-help-with-a-search-query-with-only-using-Advanced-search/qaq-p/1659444

It comes all down to the question if you have an App from Marketplace installed which is capable to do the query needed - this is because out of the box Jira does not offer the functionality you are looking for.

For example, a very popular one is ScriptRunner and you can use the functions provided by this App to query for the information you are looking for.

Please take some time to review the documentation to get a first idea what is possible:

https://scriptrunner-docs.connect.adaptavist.com/jiracloud/jql-aliases.html

There might be more Apps available from Marketplace capable of doing the same, however I am not familiar with them.

Regards,
Daniel

Faisal_onugxg · Answer

Hi Joseph,

I am aware that, once we open an individual issue then we can open a linked ticket. My requirement is to see it in the listed format.

Regards,

Faisal

Joseph Chung Yin · Answer

@Faisal - If that was the case, the user will need to access the issue directly in your JSM project UI to see the linked issue. The UI URL should be something like https:///browse/. This will take them to the JSM issue in your JSM project UI and not the portal UI. If they access the Portal UI, they should be able just clicking on the actual JSM issue key to access the JSM project UI of the specific issuekey. NOTE - If they need access to the JS issue, then they will also need access to the JS project too. Hope this helps. If my answer helped, please accept my answer of this ask. Best, Joseph