In our organization, we manage multiple Jira projects, each with its own set of versions. We use the "Fix Version" and "Affects Version" fields to track issues associated with specific releases. However, we are releasing one large embedded system that requires us to coordinate releases across all projects effectively.
A key use case an executive is interested in is understanding the impact of shifting the overall release date. For example, if the overall release (affecting multiple projects) is delayed, they want to identify what issues, such as bugs, are now planned to be fixed within the newly available time frame.
I’m looking for a way to query all issues associated with releases scheduled to go out before a given date across multiple projects. The goal is to facilitate better planning, manage dependencies, and ensure alignment for the larger system release.
We prefer solutions using native Jira functionalities (e.g., JQL or dashboards) without requiring the purchase of add-ons. Additionally, we’d appreciate any advice on alternative process approaches or tips for achieving this coordination goal more efficiently.
What strategies, tools, or processes have you found effective for managing releases across multiple Jira projects in scenarios like this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.