-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
16
-
There is a usual scenario where the customer has multiple Jira instances connected via Application Links, however, by design, the JQL queries only search for data on the instance you're accessing at the moment.
Therefore, it would be very helpful, if we had the ability to search across all Jira instances, as we can link an issue and search for them on the target Jira instance.
- mentioned in
-
Page Failed to load
[JRASERVER-72751] JQL search across multiple instances
Specially, I need the ability to search for issues in a local instance that are linked to specific issues in a remote instance. That information is available when viewing the issue details in the local instance, so I don't understand why this is so hard. I'd like the "linkedIssues" function to just "work" with remote issue keys.
Another vote for this, as our institute has several Jira instances, but needs to see workflows across all.
(There is also a Jira Cloud ticket for this - https://jira.atlassian.com/browse/JRACLOUD-79909 )
This would be very helpful to get an overview about all ticket status for more complex workflows. E.g. multiple departments or subsidiaries in a larger company are involved.
This would be great, and make my life much more simple. For example, I am a Scrum Master for multiple teams, which have at least 5 different instances of JIRA, that track different silos within the same org, and being able to have a tool to be able to query all 5 instances, for an easier to get status' and manage rollup reports, would be so helpful, and save a lot of time.
I agree, given the ability to link Jira systems via application links so that issues between those systems can be linked... it seems a glaring oversight that you cannot display information from both systems in a Kanban board or Advanced Roadmaps Plan.
This would have a high value for complete CI as CI is using for each solution / product an own project - cross over multiple instances. In order to search relevant developments / issues for an whole E2E process. Anything else is workaround and needs additional effort.
I would rate this as an extremely desirable feature.