If there are no versions set in the issues, you can choose to release the issues to a new version. A list of unreleased versions will be displayed, depending on the versions that are set for the issues in the right-most column. Go to the project that your version is in.Ĭlick the Release menu. In a Kanban project, the version will contain all issues that are 'Done' (i.e. It doesn't automatically modify the issues in the version in any way. Releasing a version on a Scrum board marks the version as released. If there are unresolved issues, you can choose to ignore these issues and proceed with the release, or move them to a later version. On the version page, click the Release button.Įnter the details for the release, then click the Release button. Go to the project that your version is in, and then click Releases > your desired version. Releasing the version is just a matter of marking the version as released. Issues are assigned to the version throughout development. In a Scrum project, a version is created when you start work on the project. Release your version in Jira Softwareīefore you release your version, check the release status of your version. You must be a Jira administrator or a project administrator to do the Jira Software tasks on this page. To deploy a release, you would typically release the version in Jira Software, build the release, then deploy the release to the required environment. By this stage, you should be confident that your version is ready to be released - issues are complete, code is checked in, reviewed, and merged, builds are passing, etc. It's time to turn your team's hard work into a software release.

Software release pack 4.07 is available