We are starting to use ARM (Jira Core v8.13.2 and ARM v3.29.8) to track multiple initiatives. We follow the Initiative->Epic->story hierarchy and I've created 'Cross Project Releases' for milestones that we would like to include on the roadmap. Example milestones are cross project events - Approval of Design Wireframes, Prototype Demonstration, Deployment. Adding the Epics and Initiatives to milestones seems to some of them "Off Track" immediately.
From https://community.atlassian.com/t5/Advanced-Roadmaps-questions/How-is-Release-Status-on-track-off-track-calculated/qaq-p/1139636
Release status is calculated based on the target dates of any issues assigned to the release. Here are the definitions:
Released - If the release is Released (i.e. released in Jira) then it's status is not calculated. The release status is only calculated for the Unreleased releases.
On-track - If the all issues assigned to the release are starting and finishing before the release date then the release is on-track. Also if there are no issues assigned to the release or none of the issues assigned to the release has dates then also it will be on-track.
Off-track - If any of the issues is starting or ending beyond the release date then the release is off-track.
Just note that currently the issue status is not taken into account and the release status is purely calculated based on the target dates set on the issues assigned to it. We are trying to improve this behavior, so keep following the documentation.
Is the only way for accurate "On Track" "Off Track" to include the milestone date as the Target End Date on each applicable Requirement/Story/Task? Will milestones always appear "On Track" if requirement/story/task do not have target end dates filled in?
