Planning a version

Still need help?

The Atlassian Community is here for you.

Ask the community

You've got a backlog full of exciting stories that are just waiting to be turned into an amazing application. It's time to plan a version! 

The documentation in this section will help you set up a new version for your Jira Software project. This includes creating the version, setting up epics, and assigning work to a version.

Search the topics in 'Planning a version':

 

Creating and configuring a version

A version is a set of features and fixes released together as a single update to your application. Assigning issues to versions helps you plan the order in which new features (stories) for your application will be released to your customers.

Learn more: Configuring versions in a Scrum project and Configuring versions in a Kanban project

Working with epics

An epic captures a large body of work. It is essentially a large user story that can be broken down into a number of smaller stories. In Scrum projects, for instance, it may take several sprints to complete an epic. You might use epics to capture broader themes in a release, e.g. performance-related work for Scrum projects, and quarterly audit-related work for Kanban projects.

Learn more: Working with epics

Branching your repository

You can use a number of different branching strategies, including task branching, feature branching, and release branching. You'll need to decide how much work should be contained in a branch before merging, when deciding on a strategy.  

If you decide to use the release branching model, you'll create your branches at the start of a version. For example, you might create a branch for your last version, so you can continue with bugfix work on that branch, while new development work is done on the master branch.

Learn more: Using branches in Bitbucket Server (Bitbucket Server documentation), Branching a repository (Bitbucket Cloud documentation), Creating and deleting branches (GitHub documentation)

Tip: You can create a branch via an issue, if Jira Software is connected to Bitbucket Cloud, Bitbucket Server, or GitHub.

Already planned a version?

Next: Get to work!

Project lifecycle

  NEW PROJECT   BACKLOG    NEW VERSION    WORK    RELEASE    REPORTING

Last modified on Jan 30, 2018

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.