Purpose
ReleaseLint helps a release manager inspect the visible direct issue dependencies for one Jira project version. It presents evidence for a human release review and never changes Jira or approves a release.
Run a review
- Open the Jira project that owns the version.
- Select ReleaseLint from project navigation.
- Choose a non-archived version.
- Choose the Jira link label and direction that means the release issue depends on the linked issue.
- Select Run dependency review.
The result shows visible open dependencies and may add context when the release issue is Done, the dependency is outside the selected version, or its due date is after the release date.
Interpret the result
An empty result means no finding was produced from the visible direct links and selected semantics at scan time. It does not prove release safety: missing links, hidden issues, tests, deployments and transitive dependency chains remain outside the review.
Use search and filters to focus the table. Select an issue key to open it in Jira. Use Export CSV to download the current view for a human review record.
Limits
- Direct links only; no transitive traversal or missing-link inference.
- At most 500 visible release issues and 500 unique direct dependencies per review.
- Jira indexing may delay a recently changed issue.
- Jira permissions determine what the current user can inspect.
- CSV files are managed by the customer after download.
Troubleshooting
- No versions: create or unarchive a project version in Jira.
- No link types: ask a Jira administrator to enable and configure issue linking.
- Unexpected direction: choose the opposite inward or outward label and rerun.
- Recent status missing: allow Jira indexing to complete, then rerun.
- Size-limit error: review a smaller project version; ReleaseLint does not return partial success.
Get support
See the support policy and contact channels.