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.
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:
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:
There might be more Apps available from Marketplace capable of doing the same, however I am not familiar with them.
This may not be possible because JSM customers for your end (they don't need license for JSM). Where they access their issues only via the portal UI and not the actual JSM project UI. In addition, one must have a license for Jira Software to access your JS projects. There is no way that I know of to expose Linked issues information via the JSM portal.
You may include the JS bug issue URL in your JSM issue's as a comment, however your customer will not be able to access it unless they have Jira Software licenses.
Hope this helps.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Infrastructure Applications Team
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://<your based address>/browse/<the JSM issue key>. 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.
Hi Everyone, In this tutorial, we will show you how you can monitor an SLA, and send notifications before or after the SLA has been breached. SLA Threshold Trigger The SLA t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events