Note: This article has been deleted and re-published to send a new notification, as the release timeframe for these changes has been updated.
For versions 10.100.1 and later, we'll be making some big changes to objective statuses that will also affect the API:
What’s coming in version 10.100.1
In this release, we will be adding three new statuses to objective tracking in Jira Align. These statuses will provide more nuance to the status of objectives than our current option (In Progress) allows. The new statuses will be:
On Track: Indicates that an objective is likely to reach its desired outcomes.
At Risk: Indicates that an objective has uncertainty around reaching its desired outcomes. For example, work needed to complete the objective may be behind schedule, or risks might pose a future threat to completion.
Off Track: Indicates that an objective is unlikely to reach its desired outcomes if action is not taken.
In version 10.100.1, the new statuses will become available in the Jira Align UI, and will not change any existing status values. API users should also note that the status endpoint will include the new statuses, and no statuses will be removed or changed for this release.
We strongly recommend that you review your in-progress objectives and update any objectives that are at risk or off track, as the In Progress status on objectives will be migrated in a future release.
What’s coming later
In a future release, any remaining In Progress objectives will receive the On Track status. At this time, the API status value for In Progress will also be removed.
What this means for the API
Any objectives with the In Progress value will now return as On Track. There are also two new values: Off Track and At Risk. In any scenarios where the In Progress value is specified, there would need to be a change to specify On Track and depending on the use case, include the new status values as well. Otherwise, there is no action needed with this change.
Why are we making this change?
This change is in preparation for a new end-to-end objective experience including a new creation workflow, a cleaner Details panel, and a more powerful objective tree experience. As we continue to respond to feedback, it has been evident that we need the ability to provide better status updates around objectives.
For our customers utilizing OKRs, the objectives often appeared to be “at risk” when they had low scores, even if it was just too early in measuring. These new changes, along with the updates to the objective tree around the corner, will provide a much clearer picture of which objectives need attention (and which don’t) when reporting on status.