Learn how to set up Jira Software Cloud and integrate it with other products and applications.
Learn how to configure your Jira Software Cloud company-managed projects to suit your agile development processes.
Learn how to create, search, and work with issues in software projects, manage your profile, and more.
Learn how to get started, enable features, and manage and administer team-managed projects.
Plan and view work across multiple teams, projects, and releases with Advanced Roadmaps.
A guide on how to deploy and monitor an application built on AWS using Atlassian and third-party tools.
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.
In Jira Software, versions are managed via the Releases feature.
To view the release page for a version:
Log in to your Jira Software project
Select Releases from the side menu.
Select a version to view its release page.
On the release page for a version, issues are grouped into tabs, depending on whether they are 'To Do', 'In Progress', or 'Done'.
An issue will appear under 'To Do', 'In Progress', or 'Done' according to the issue’s status and status category. For example, the status 'Open' may have its status category set as 'To Do'. Therefore, it will display on the release page in the 'Issues to do' tab. Learn more about issue statuses in Jira and how to configure them.
Add links with the Related work feature
The Related work feature allows you to add links to your version, so your team members and stakeholders can easily find documents, dashboards, and anything else related to the release. For example, you might add links to release notes, analytics dashboards, design specifications, and relevant support documentation.
Adding links to a version:
Log in to your Jira Software project and go to your version.
Select Add in the Related work section.
Enter the URL for the work you want to link.
Add a description (this step is optional).
Select a category and save.
If the link is from a provider that’s supported by our Smart Links feature, we’ll fetch the description, last updated date, provider name and logo from the document you’ve linked to. For all other links, we’ll display a generic icon and the description that you entered when adding the link.
You must have project administrator permissions to add links to a version.
View warnings on the release page
Issue warnings tell you when your issue data is potentially out of sync with your development data. Depending on which development tools are connected to Jira Software, the release page will display the following warnings:
Open pull requests - An issue is done, but has an open pull request.
Unreviewed code - An issue is done, but its commits are not part of a pull request or code review.
Failing builds - An issue is done, but is linked to a failing build.
Open reviews - An issue is done, but has open reviews (you’ll only see this warning type if you’re using the Fisheye-Crucible integration with Jira Software).
Warnings will only display on the release page if:
Jira Software is connected to your development tools, e.g. 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. You can see which warnings are enabled by clicking the Manage warnings button. You must have project administrator permissions to enable or disable warnings.
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:
Jira Software 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 an SCM tool like Bitbucket or GitHub, you’ll see the number of commits, branches, and pull requests associated with each issue in the Development column. We’ll also show the pull request status (e.g. OPEN, MERGED, DECLINED). Click on 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 Builds column. 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 Deployments column. 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 Feature flag column. 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 Feature flag column will show the flag icon and the total number of flags linked to the issue. Hover over the flag to view more info, or click to view a detailed dialog with links to the associated flags in your feature flag tool.
Release a version
To release a version, go to your project > Releases > your desired version, and select ‘Release’. Releasing the version will mark it as 'Released' in Jira Software. You will have the option of setting a release date and moving any incomplete issues to another version.
Was this helpful?