-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
User Problem
Currently, Jira Align restricts Program Objectives to a single Program Increment (PI) and limits them to a single Program, creating challenges for teams working on long-term, multi-quarter initiatives. This limitation requires teams to duplicate objectives for each PI, adding unnecessary workload and reducing alignment on complex, shared objectives across multiple teams. Without the ability to set shared objectives across PIs and programs, organizations struggle to maintain cohesive tracking and execution of extensive projects that require contributions from various programs over an extended period.
Suggested Solutions
- Multi-PI Support for Program Objectives: Allow program objectives to be associated with multiple PIs, enabling teams to manage objectives that span several quarters more efficiently.
- Cross-Program Objective Assignment: Enable program objectives to be assigned to multiple Programs, making tracking and managing objectives that involve cross-program collaboration and shared goals easier.
Current Workarounds
Users must create duplicate Objectives for each PI and each Program involved, leading to a fragmented approach to tracking long-term initiatives. This workaround introduces additional administrative overhead and risks misalignment as teams manually manage and coordinate shared objectives outside Jira Align.
[JIRAALIGN-7744] Enable Program Objectives to span multiple PIs and Programs in Jira Align
Features are designed to take more than one Sprint to complete, so I support estimating Features to be completed within one PI.
Objectives, on the other hand, are aspirational "moon shots" and not BAU. They should aim for delivery with measurable, quantifiable key results. It makes sense for Jira Align to allow a Product Manager to update the "Planning Increment" Field to add an additional PI when necessary. For example, at the end of a PI, if the Product Manager realizes the OKR achieved 80% of its intended Key Result of 95%, they should be able to update the Objective Tree to the next PI to stay on course for full delivery of the OKR. Deleting the "Work in Progress" from the prior PI, despite nearly delivering the entirety of the OKR, is not good product management. Furthermore, the "Due Date" field is limitless, allowing any date to be picked, yet the PI Field is restricted to one PI. This inconsistency does not make sense.
Please, for the sake of Product Managers, allow the OKR field in Jira Align to span multiple PIs for reasons addressed above.
Program Objectives and Features are Program level items that are designed to be completed in a single PI. To make this change would go against the intended purpose of Program Objectives and Features.
This is foundational to how many teams work. I highly doubt that every Atlassian team is able to finish all features related to an objectives in a single PI