Learn how to set up Jira Software Cloud and integrate it with other products and applications.
Versions represent points in time for your project. They can be used to schedule how features are rolled out to your customers, or as a way to organize work that has been completed for the project.
Versions in are managed using the releases feature. Learn how to enable the releases feature
To check the progress of a version:
From your project’s sidebar, select .
Select your version from the list.
Check the progress of your issues and related work in the Progress section.
Using the progress bar, you can see a summary of issue status (done, complete, warnings) and related work status (added, placeholder).
Approve or decline the work in a version
If you’ve been added as an approver, you can approve or decline the work in the release.
Approval indicates you’re happy for the release to go ahead, and declining means you think changes are needed first.
Select a release from the list.
Find your name in the Approvers section, and select Waiting.
Select either Approve or Decline (and add an optional reason if you decline).
Your approval status will now be updated in the approval section, and you can update it again by selecting it.
Warnings appear when your issue data is potentially out of sync with your development data.
Warnings appear if:
is connected to your development tools (like Bitbucket, GitHub, GitLab, or Jenkins).
Learn more about integrating with development tools
You have the View development tools permission.
Learn more about Jira permissions
Warnings are enabled. To view the warning types that are enabled, go to the Issues section of your version, select the actions icon () on the right, then the settings icon (). You must be a project administrator to do this.
Depending on which development tools are connected to , you can view different warning types:
Open pull requests (an issue is marked as done, but it has an open pull request).
Unreviewed code (an issue is marked as done, but its commits aren't part of a pull request or code review).
Failing builds (an issue is marked as done but it's linked to a failing build).
Open reviews (an issue is marked as done but it has open reviews).
Open review warnings will only appear if you are using a Fisheye-Crucible integration with .
View development information on the release page
The release page will display the commits, branches, pull requests, builds, and deployments related to each issue in your version, provided that:
is connected to your development tools, and
your team includes issue keys in their branch names, commit messages, and pull requests.
Commits, branches, and pull requests
If you’ve connected a source code management (SCM) tool like Bitbucket or GitHub, you can view the number of commits, branches, and pull requests associated with each issue in the Issues section.
We’ll also show the pull request status (e.g. open, merged, or declined). Select a piece of dev info to view a detailed dialog with links to the commits, branches, or pull requests in your SCM tool.
If you’ve connected a build tool like Bitbucket, GitHub, or GitLab, you’ll see the build status for each issue in your version in the Issues section.
We’ll show an icon to indicate whether the build was successful , failed, or unknown. Click on a build icon to view a detailed dialog with links to the associated pipelines in your build tool.
If you’ve connected a CI/CD tool like Bitbucket Pipelines, GitHub, GitLab, or Jenkins, you’ll see the deployment status of each issue in your version in the Issues section.
We'll show an icon to indicate whether an issue has been deployed successfully and a label to tell you what environment it’s been deployed to. Click on a deployment status to view a detailed dialog with links to the associated pipelines in your CI/CD tool.
If you’ve connected a feature management tool like LaunchDarkly or Split, you’ll see a flag icon and a percentage in the Issues section.
The icon indicates whether a flag is enabled or disabled, and the percentage shows the current rollout of a particular flag. If you have more than one feature flag linked to an issue, the number of flags linked will be shown instead of a rollout percentage. Hover over the icon to see quick info about connected flags, and select it to view full details.
Release a version
You must have project administrator permissions to release a version.
To release a version:
From your project’s sidebar, select .
Select the version from the list.
Select the version’s current status (for example, Unreleased) and then select Release.
Confirm what to do with any unresolved issues, and enter a release date.