Learn to plan and estimate for scrum teams

In this section

Plan for the team

Customize the team board

Estimate in story points

Analyze team reports

Optimize future plans

Related content

Leading an agile project

Getting started as a JIRA Software user

Working as a team member in an agile project

JIRA Software overview

Getting started with JIRA Software

Estimating and planning for agile projects can be really challenging regardless of how experienced you are. There's always competing
priorities, resourcing issues, business demands and time constraints.

This topic can't make any of those things go away, but if you're a newish to agile scrum or just new to JIRA Software, it will give you
an overview of the JIRA Software features to help you plan and estimate.
 Learning objectives

The aim is to give you a good introduction to:

Planning concepts and functions

Estimating methodologies
Analysis tools and techniques
Optimization approaches

We've also asked some of our Atlassian teams to provide some tips and advice along the way.

Learning activities

There's optional activities outlined at the bottom of each topic. You don't have to do these, but it does help to put the theory into practice.
You might want to create a dummy project to do this.

Pre-requisites

You need:

Access to JIRA Software are. If you don't have a working copy, trial it here.
The ability to create projects and configure boards.
If you are working with an existing instance of JIRA software, you need this access to do some activities. If you create a dummy project, you
will get this access by default.
Let's go
Learn more about agile

It helps if you're familiar with the agile language and concepts we'll use. So if this is a bit new to you or you feel a bit rusty, check out
the Agile Coach, which covers lots of the basics.
 Leading agile projects
In this section

Starting a new project

Building a backlog

Organizing work with versions

Planning a version

Getting to work

Releasing a version

Reporting

Related content

Working in agile projects

JIRA Software overview

Setting up JIRA Software

Configuring a project

What is a board?

Checking the progress of a version

You may be the iteration manager, product owner, agile coach, or team lead for your team if you are responsible for running an
agile project with Jira Software, you are in the right place! The topics in this chapter will help you configure your existing Jira
Software instance to suit your agile development process.
 In the wrong place? See the following chapters instead:

If you are a team member working with Jira Software, see Working in agile projects.
If you are an administrator installing or configuring the Jira Software server, see Administering Jira Software.

Where do I start?
If this is the first time you're using Jira Software, check out I lead a software team before you start reading other topics.
If you're already familiar with Jira Software, start with Starting a new project to set up your project, or use the search box below to find the topic
you need.

The topics in this chapter cover the activities that you will need to do in each stage of the agile development lifecycle:

Starting a new project

Time to get everything set up! This is the stage where you create a new Jira Software project, configure your development tools, e.g.
create repositories in Bitbucket, and determine how you will manage documentation and team calendars.
Learn more...
Building a backlog
A backlog is a list of outstanding work. Before starting new work, you will build a new backlog or groom an existing backlog. This
involves creating, ranking, and estimating issues, so that you have a prioritized list of tasks to work from.
Learn more...
Planning a version
Ready to start work on a new version? To plan a version, you need to set up the version in Jira Software and configure your
development tools appropriately, e.g. branch your repository.
Learn more...
 Getting to work
All systems go! Once work begins, you will be running sprints and tracking your team's progress. For teams using Scrum, this
involves planning and starting sprints, monitoring sprints via boards and charts, and completing sprints. For teams using Kanban, this
involves monitoring the work in progress, and limiting work to the constraints for your team, via boards and charts.
Learn more...
Releasing a version
This is the culmination of your team's hard work. Before releasing a version, you would typically check if there is outstanding
work for the version. If everything's good to go, you can then deploy the version, and create the related release reports and
documentation.
Learn more...
Reporting
Reporting is an activity that occurs throughout a development cycle. You may need to make reports available to different stakeholders
or use them yourself. Jira Software has a number of reports that you can use to provide different information about the progress of
your team's work.
Learn more...
Last modified on Sep 12, 2017

Starting a new project

In this section

Configuring a project

Configuring development tools

Configuring collaboration tools

Related content
 Getting to work

Working in agile projects

JIRA Software overview

Setting up JIRA Software

Planning a version

What is a board?

It's time to start your project! You know what you need to do, and you have a team that is excited to start working. You want to get
everyone off to the best start, so let's make sure that your systems are set up and ready to go.

The documentation in this section will help you configure Jira Software for a new agile development project. This includes creating a
new Jira Software project, configuring a board (Scrum/Kanban), configuring your development tools to work with Jira Software, and
more.

Note: it is assumed that you already have a Jira Software instance. If you don't have Jira Software, install Jira Software Server (Setting up
Jira applications) or sign up for a Jira Software Cloud site account.

Creating or configuring a Jira Software project

A Jira Software project is simply a collection of issues (stories, bugs, tasks, etc). You would typically use a project to represent the
development work in Jira Software. This could be the work related to a product, a team, etc.
Learn more: Configuring a project
Setting up your repositories, build plans, and review projects
The start of a project is where you would set up new repositories in Bitbucket or Fisheye, create build plans in Bamboo, and perhaps
create new review projects in Crucible (if you are not using Bitbucket). If you're using alternative tools, consult your vendor's
documentation.
Learn more: Create a repository (Bitbucket Cloud), Creating repositories (Bitbucket Server), Configuring plans (Bamboo), Creating a
project (Crucible)
Connecting your development tools to Jira Software
Jira Software can be connected to a range of development tools to help you keep your project tracking in sync with your development
work. For example, if you have Bitbucket connected to Jira Software, you can configure issues to automatically transition when
commits are made.
Learn more: Configuring development tools
Connecting your collaboration tools to Jira Software
Every software project requires collaboration, whether it be via chat rooms, online documentation, or team calendars. If you
have Hipchat (chat), Confluence (wiki) and/or Team Calendars for Confluence (calendars), you can connect them to Jira Software to
help you plan and run your project more efficiently. For example, you could get issue notifications in your chat rooms, link
specifications to epics or retrospective notes to sprints, include team events on your project calendar, and more.
Learn more: Configuring collaboration tools

Already set up your project?

Next: Start building a backlog
Project lifecycle
NEW PROJECT BACKLOG NEW VERSION WORK RELEASE REPORTING
Last modified on Oct 10, 2017

Was this helpful?

Yes

No

Provide feedback about this article

 Configuring a project
In this section

Editing a project's details

Creating a board

Configuring a board

Workflows

Organizing work with components

Customizing the issues in a project

Related content

What is a board?

Configuring development tools

Creating issues and sub-tasks

Permissions overview

Monitoring work in a Kanban project

Leading agile projects

Your issue tracker should be the hub of your development project. When properly configured, Jira Software helps your team members
prioritize and organize work better, so they can spend more time developing great software instead of wrangling issues.
 A project is simply a collection of issues (stories, bugs, tasks, etc). You would typically use a project to represent the development
work for a product, project, or service in Jira Software.

Scrum, Kanban, Bug tracking, or agility*?

Scrum has an iteration-based approach, which is generally a good fit for teams developing products, particularly if your team is releasing new
versions on a regular schedule.
Kanban is better suited for a continuous flow of work (e.g. service-oriented teams), where its constraint-based approach helps prevent your team
from being overloaded.
Bug tracking delivers a basic workflow for tracking new features and bugs.
Agility* delivers a simplified board-view project template which is straight-forward and streamlined, providing more power progressively as you
need it.

*Beta version. If you don't have access to the agility board yet, don't worry you will soon.

Before you begin

Ideally, you should be a Jira administrator (i.e. someone with the 'Jira Administrators' global permission), if you want to set up a
new project in Jira Software. Many of the tasks involved can only be performed by a Jira administrator, such as creating a project,
modifying a workflow, etc. For more information, see Permissions overview.

The topics in this section cover the activities that you will need to do when configuring a project.

Create a project
Your first task is to create a Software project and configure it according to the needs and requirements of your development
team. You need to be a Jira administrator to create a project, but you can configure most project details (e.g. name, avatar, etc) if you
are a project administrator.
Learn more: Configuring projects (Jira admin documentation)
Configure the board for your project
A board is the central tool for working with issues in a Scrum or Kanban development project. A Scrum or Kanban board will be
created when you create a Scrum or Kanban development project respectively. You can add more boards of either type to the project,
if you like.
Learn more: Configuring a board
Configure project permissions
You can control access to your project by configuring a permission scheme. A permission scheme maps users, user groups, roles, etc
to the project functions (e.g. Assign issues). Your new project will be pre-configured with the default permission scheme.
Learn more: Managing project role memberships
Tweak issue types, workflow, screens, and fields
Your project is pre-configured with issue types, a workflow, screens, and fields. You can change these to suit any development
process. For example, you may want to create a 'Design' issue type or add a 'QA review' step to your workflow.
Learn more: Defining issue type field values, Workflows, Defining a screen, Jira custom fields (Jira admin documentation)
Create components
Components can be used to group issues in a project. However, in an agile project, you should consider using epics to group issues
(stories) instead, as there are more features that support working with epics, like the epic column on boards, reports, etc.
Learn more: Managing components
Last modified on Oct 10, 2017

Was this helpful?

Yes

No

Provide feedback about this article

Editing a project's details

 Related content

Configuring a project

As a project admin, you can edit your project's:

Name
Key
URL
Project type
Project category
Avatar
Description
Project lead
Default assignee

To edit a project's details:

1. Go to your project's settings.

2. Select Details.
3. Make your edits.
4. Select Save details.

If you change the name of your project, the new name will automatically update in any filters on your Jira site.

Change your project's key

Some Jira applications will start a background re-index when you save your updated project key. It's best to change a key during a lull
on your site to prevent performance issues.
 To change your project's key:

1. Go to your project's settings.

2. Select Details.
3. In the Key field, enter your desired key. Your project's key must be at least 2 characters long and contain only uppercase letters.
4. Select Save details.

After you change a key, we recommend communicating the change to your users. For example, board filters and dashboard filter
gadgets need to be updated with the new key.

Link to more project details with a project URL

You can link team members and viewers to an external site by adding a project URL. The project URL displays on
the Summary page of some projects, and in the Projects directory of your site.

Most teams supply an address to documentation about the project, roadmaps or other important content outside of their Jira site. If you
use Confluence to collaborate, we recommend adding a link to your team's space.

To change your project's URL:

1. Go to your project's settings.

2. Select Details.
3. In the URL field, enter your link.
4. Select Save details.

Add a project description

Team members and visitors can view a project's description in the Summary page of some projects. And, administrators can view the
description in the Summary section of your project settings.
 To add or edit your project's description:

1. Go to your project's settings.

2. Select Details.
3. In the Description field, enter a brief, detailed explanation of the project.
4. Select Save details.

Change your project's type

If you have multiple Jira apps on your site, you can choose to change your project's type. For example, if you have both Jira Core and
Jira Software, you can upgrade a business project to a software project and get finer control over your project's workflow, board
settings and more.

Changing a project type means changing the way your users work in that project. It's much easier to create a new project than change a
project's type after extended use.

Read more about project types and what makes them different.

To change a project's type:

1. Go to your project's settings.

2. Select Details.
3. In the Project type field, select the type of project you want to change to.
4. Select Save details.

Add or edit your project's category

Your Jira admin may add project categories to help manage projects across your Jira site. If they've added categories, you can assign
your project to one of them in your project's details.
 To change our project's category:

1. Go to your project's settings.

2. Select Details.
3. In the Category field, select the appropriate category from the drop down.
4. Select Save details.

Change your project's avatar

Avatars help give a face to your project's name. They appear in the project sidebar and in your site's list of all projects.

To change your project's avatar:

1. Go to your project's settings.

2. Select Details.
3. In the Avatar field, select your current avatar.
4. Choose from a default icon or upload your own.
5. Select Save details.

Change the project lead

A project's lead is usually the project administrator, who controls and manages a project's settings.

You may want to change the project lead as people move in and out of your team in longer-term project.

To change your project's lead:

1. Go to your project's settings.

2. Select Details.
3. In the Project lead field, set a new person to lead the project.
4. Select Save details.

Add or change your project's default assignee

When issues are created in your project, you can set a default assignee. This is useful for open projects where everyone on the site can
report tasks to your project.

The default assignee is typically a team member who prioritizes or validates that reported issues are meant for their team and
distributes these tasks to their team members accordingly. By default, they receive notification when someone creates an issue in the
project.

To change your project's default assignee:

1. Go to your project's settings.

2. Select Details.
3. In the Default assignee field, nominate your project's default assignee.
4. Select Save details.

Last modified on Sep 28, 2017

Was this helpful?
Yes

Creating a board
On this page

Before you begin

Creating a new board

 Copying an existing board

Example JQL queries for board filters

Next steps

In this section

What is a board?

Related content

Configuring a board

Monitoring work in a Kanban project

Using your Kanban backlog

Permissions overview

Configuring filters

Creating issues and sub-tasks

You need a board so that you can view and work on issues in Jira Software. A board displays issues from one or more projects. You
can either copy a board that someone else has created, or create a new board for yourself. You can also create as many boards as you
like.

There are four types of boards:

Scrum boards: For teams that plan their work in sprints. This project template delivers a board and a backlog.
Kanban boards: For teams that focus on managing and constraining their work-in-progress. Kanban boards don't have a separate Backlog view
by default. Initially, you use the first column of the board as your backlog, and as your team grows or if you're planning for many issues for
your team you can choose to enable the Kanban backlog. This way, you get a bigger space to plan work for your team.
 Bug tracking (formerly 'Basic'): For teams who just need a basic workflow to start tracking new features and bugs. This project template uses a
list, rather than a board.
Agility (beta version. If you don't have access to this board yet, don't worry you will soon): For teams who are new to agile. Get your team
up-and-running with this simplified board-view project template. The set-up is straight-forward and streamlined, delivering more power
progressively as you need it.

Learn more: What is a board?

Before you begin

Any user can create a board, but certain permissions are required to share the board with other users:

If you create a board via Boards (in header) > View All Boards, you won't be able to share it, unless you have the 'Create Shared Objects' global
permission.
If you create a board via the following methods, you don't need the 'Create Shared Objects' global permission to share the board:
o Creating a project, where a board is created for the project by default
o Setting up Jira Software for the first time, where you're prompted to create a project, which also creates a board for the project
o Copying a board, where the copied board will be shared with the same users as the original board

Creating a new board

1. Log in to Jira Software.
2. If you're setting up Jira Software for the first time, do either of the following actions. Otherwise, please continue.

o If you're creating either a Scrum software development project or a Kanban software development project, follow the prompts to create your
project. A board is created for your project by default.
o If you're creating an agility software development project, follow the prompts to create your project. After your project is created, click Create
board under your project name, and follow the prompts to create your board.
3. Select Boards > View All Boards from the top navigation bar.
4. Click Create board at the top-right of the page, and choose whether to create a Scrum board or Kanban board, as described
below. Note that you cannot change the board type after creation (that is, a Scrum board cannot become a Kanban board, and vice
versa).
To create a Scrum board based on projects

To create a Kanban board based on projects

To create a Scrum or Kanban board that is based on a filter

5. Your new board will be shown. At the top is a link that you may want to send to other people so that they can use your board.

Congratulations you have created a new board!

Copying an existing board

If you would like to create a board that is similar to one you are already using, you can simply create a copy.

Your new board will be based on the same issue filter as the original board. You will be the administrator of the new board, but not
necessarily of the filter, so you may not be able to edit the filter. However, once your new board is created, you can easily choose a
different filter (e.g. to view a different project) see Configuring filters.

1. Select Boards > View All Boards from the top navigation bar.
2. The All boards screen will be displayed. Click the Copy link corresponding to the board of interest.
 Alternatively, to quickly create a copy of the board you are currently viewing, simply select Copy from the Board menu at the top
right of the page.

Example JQL queries for board filters

Here are a few common queries that you can use for your board's filter:
Select all issues that are Unscheduled or in an Unreleased Fix Version:
project = JSW AND (fixVersion in unreleasedVersions() or fixVersion is empty
Select all issues you are interested in:
(assignee = currentUser() or reporter = currentUser()) AND (fixVersion in unreleasedVersions() or fixVersion is
empty)
Show all issues that you have participated in and have been updated in the last week. This requires the Jira Toolkit add-on.
updatedDate > -7d AND Participants = currentUser()
Select all issues for a team (using a Label custom field named 'Team')
(team = ateam or team = dreamteam or team = engineroom) AND (fixVersion in unreleasedVersions() or fixVersion is
empty)
Only select my bugs for a bugfix team
project = JSW AND team = bugfix AND issuetype = bug AND (fixVersion in unreleasedVersions() or fixVersion is empty)
Try fixVersion = earliestUnreleasedVersion(PROJECT KEY) to see all issues in the next Fix Version to be released:
fixVersion = earliestUnreleasedVersion(PROJECT KEY)

See JQL for more information on using JQL for your board. Let your imagination run wild!

Next steps
Need help? If you can't find the answer you need in our documentation, we have other resources available to help you. See Getting
help.

Read the following related topics:

 To learn more about your new board, see What is a board?
If you wish to make any changes to your new board, see Configuring a board.
If you wish to make any changes to the issue filter for your board, see Configuring filters.
To learn more about adding a column to your board, see Configuring columns.

Last modified on Oct 10, 2017

Was this helpful?
Yes

No

Provide feedback about this article

In this section

What is a board?

Related content

Configuring a board
On this page

Before you begin

Accessing a board's settings

Renaming a board

Changing a board's administrators

Sharing a board
 Next steps

In this section

Configuring filters

Enabling ranking

Configuring columns

Configuring swimlanes

Configuring Quick Filters

Customizing cards

Configuring estimation and tracking

Configuring the issue detail view

Configuring working days

Related content

Creating a board

Permissions overview

Monitoring work in a Kanban project

Saving your search as a filter

Using Active sprints

What is a board?
 Configuring a board allows you to edit the mapping of workflow statuses to columns of a board, as well as edit the columns,
swimlanes, and quick filters of a board, and customize the card colors and displayed issue fields.

Before you begin

You must be a Jira administrator or a board administrator for the board to modify its configuration.

Accessing a board's settings

1. Navigate to the desired board, then select more ( ) > Board settings.
2. On the Board settings screen, select the desired tab (Columns, Swimlanes, etc).

Screenshot: the Board settings screen of a Scrum board ('General' tab).

Screenshot: the Board settings screen of a Kanban board ('General' tab).
 Renaming a board
1. Navigate to the desired board, then select more ( ) > Board settings.
2. On the Board settings screen, click the 'pencil' icon (which will appear when you hover) to edit the name of your board. Press
the Enter key when finished.
 Changing a board's administrators
A board's administrator is the only person who can change the configuration of a board along with Jira administrator users. By
default, the administrator of a board includes the person who created it. If you are a board administrator or a Jira administrator, you
can change the administrators of a board. See Permissions overview for more information.

1. Navigate to the desired board, then select more ( ) > Board settings.
2. On the Board settings screen, click any of the name(s) in the Administrators field (a 'pencil' icon will appear when you hover over
them).
3. Enter the names of the desired users or groups. If you start typing the name, a list of users and groups will be suggested. Press the Enter key
when finished.
Note, the suggested user list will not display if you don't have the 'Browse Users' global permission. However, you can still enter the user names
and group names manually. See Permissions overview for more information.

You may also want to give the new administrators rights to manage the Jira filter on which the board is based see the Jira
admin documentation on Managing shared filters.

Sharing a board
A board is available to all users who can view the saved filter on which the board is based. (Note that they will also need 'Browse'
project permission for the project(s) whose issues are shown on the board. See Permissions overview for more information.)

If you wish to share a board with different people, you will need to either edit the saved filter (see the documentation on issue filters),
or choose a different filter (see Configuring filters).

Next steps
Need help? If you can't find the answer you need in our documentation, we have other resources available to help you. See Getting
help.
Last modified on Sep 12, 2017
 Was this helpful?
Yes

No

Provide feedback about this article

In this section

Workflows
Related content

Using the Simplified Workflow

Configuring a project

All Jira projects contain issues that your team can view, work on, and transition through stages of work from creation to
completion. The path that your issues take is called a workflow. Each Jira workflow is composed of a set
of statuses and transitions that your issue moves through during its lifecycle, and typically represents work processes within your
organization.

In addition, Jira uses workflow schemes to define the relationship between issue types and workflows. Workflow schemes are
associated with a project, and make it possible to use a different workflow for different combinations of project and issue types. If
you need to edit or create a more advanced workflow to match how your team or organization works, you can log in as a Jira
Administrator with global permission to access and create your workflow.

What you can do... Documentation

 Edit existing workflows
Create new workflows
Working with workflows
Configure existing workflows

Add a workflow scheme

Configure a workflow scheme
Configuring workflow schemes
Manage workflow schemes

Import and export workflows

Activate and deactivate workflows Managing your workflows

Add custom events

Configure the initial status
Work in text mode
Configure workflow triggers
Advanced workflow configuration
Use validators and custom fields
Use XML to create a workflow
Configure workflow properties

Last modified on Sep 28, 2017

Was this helpful?

Organizing work with components

 On this page

Managing a project's components

Adding a new component

Selecting a default assignee

Editing a component's details

Deleting a component

Related content

Configuring a project

Components are used to group issues into smaller sub-sections of a project, such as user interface or API workstreams. You can set a
default assignee for a component, which will assign all new issues with that component to that person (e.g. all documentation issues
will be assigned to your technical writer).

You need to have the project-specific Administer Projects permission or the Jira Administrator global permission to be able to:

Add create a new component against which issues can be aligned

Edit change a component's details
Delete remove a component

Once a component has been created for a project, the 'Component' field becomes available for your issues. If you cannot see this field
on your issue, your project may not have any components yet, or the field is hidden from view.

Managing a project's components

The easiest way to manage a project's components is through the Components page.
1. Choose > Projects, and click the name of the project.
2. Choose Components in the sidebar. The Components page is displayed, showing a list of components and each component's details. From here,
you can manage the project's components as described below.

Adding a new component

1. The Add Component form is located at the top of the 'Components' screen.
2. Enter the Name for the component. Optionally, enter a Description and select a Component Lead and Default Assignee (see options below).
3. Click Add.

Selecting a default assignee

You can optionally set a default assignee for a component. This will override the project's default assignee for issues in that
component. If an issue has multiple components, and the default assignees of components clash, the assignee will be set to the default
assignee of the component that is first alphabetically.
Default
assignee Description Notes
option
Issues matching this component
Project will have the assignee set to the
Default same default assignee as the
parent project.

If the project leader is not permitted to be assigned to issues in the permission

The assignee will be set to the
Project Lead scheme, this option will be disabled and will say "Project Lead is not allowed to be
project leader.
assigned issues".

Component The assignee will be set to the If the component leader is not permitted to be assigned to issues in the permission
 Lead component leader. scheme, this option will be disabled and will say "Component Lead is not allowed to
be assigned issues". The Component Lead option will also not be available if the
component does not have a lead assigned to the component. Instead, under this
option, it will say "Component does not have a lead".

The assignee of the issue will not

This option will only be available if "Allow unassigned issues" is enabled in the
Unassigned be set on the creation of this
general configuration.
issue.

Editing a component's details

1. On the 'Components' screen, open the menu in the Actions column for the component you want to edit, and select Edit.
2. Edit the component's Name, Description, Lead, and Default Assignee in the Edit component dialog.
3. Click the Save button to save your changes.

Searching for a component

If you need to find a component in a long list, it's easiest to search for it. Start typing text into the search box that you know the
component contains, and your list will automatically be filtered for you.

Deleting a component
1. On the 'Components' screen, open the menu in the Actions column for the component you want to delete, and select Delete.
2. You will be prompted to associate any issues assigned to this component with another component if you wish.
3. Click the Delete button to delete the component.

Last modified on Sep 12, 2017

Was this helpful?
 Yes

No

Provide feedback about this article

Related content

Customizing the issues in a project

Related content

Editing multiple issues at the same time

Creating issues and sub-tasks

Monitoring work in a Kanban project

Working with issues

Using Active sprints

Using your Scrum backlog

Issues are the packets of work that need to be completed in a project. These issues are made up of issue fields, and the issue fields
contain data about the issue. This data is important, as it helps define the issue, and can contain important information about the issue,
such as a summary, a description, due dates, and when and where the work is required. Jira Software allows you to customize issues
by changing the configuration and behavior of these fields to suit your team's needs.

You may choose to:

Change a field's behavior (such as change a field's description, make a field hidden or visible, or make a field required or optional)
Add your own values for fields that have default values assigned (e.g. Resolution and Status)
 Create new 'custom' fields
Configure different renderers for (some) fields
Position fields on a screen
Choose which screen should be displayed for each issue operation (e.g. 'Create Issue', 'Edit Issue') or workflow transition (e.g. Resolve Issue,
Close Issue)

A simple example of how customizing an issue could benefit your team could be marking fields as 'Required' when an issue is created.
This would ensure you always capture the required information you need to get the work done to resolve the issue. If you couple this
with positioning the required fields at the top of the screen, and even hiding fields you know the issue creator won't use, you'll make
sure your users can see and complete the required fields as quickly as possible.

You can make this... ...into this!

 To customize your issues, you need to be a Jira administrator. You can review more conceptual information on customizing issues in
the Jira administrator documentation.
Last modified on Sep 12, 2017

Was this helpful?

Yes

No

Provide feedback about this article

Related content

Organizing work with versions

On this page

Managing a project's versions

Add a new version

Release a version

Archive a version

Delete a version

Merge multiple versions

Reschedule a version

Related content
 Configuring versions in a Scrum project

Configuring versions in a Kanban project

Version Report

Releasing a version

Deploying a release

Reporting

Versions are points-in-time for a project. They help you organize your work by giving you milestones to aim for. You can then assign the
issues in your project to a specific version, and build up the work you need to do to complete that version.

You need to have the project-specific Administer Projects project permission or the Jira Administrator global permission to be able to:

Add create a new version against which issues can be aligned.

Release mark a version as released.
Archive hide an old version from the Releases report, and in the user interface.
Delete remove a version. You must choose an action for any issues with that version.
Merge combine multiple versions into one.
Reschedule re-arrange the order of versions.

Once a version has been created for a project, the 'Affects version' and 'Fix version' fields will become available for your issues. If you cannot
see these fields on your issue, your project may not have any version yet, or the fields are hidden from view.

Managing a project's versions

The easiest way to manage a project's versions is through the Versions page.
1. Choose > Projects, and click the name of the project.
2. Choose Versions in the sidebar. The Versions page is displayed, showing a list of versions.

Screenshot: The 'Versions' page

Add a new version

1. The Add Version form is located at the top of the 'Versions' page.
2. Enter the name for the version. The name can be:
o simple numeric, e.g. "2.1", or
o complicated numeric, e.g. "2.1.3", or
o a word, such as the project's internal code-name, e.g. "Memphis".
3. Optional details such as the version description (text not HTML), start date and release date (i.e. the planned release date for a version) can be
also be specified. These can be changed later if required.
4. Click the Add button. You can drag the new version to a different position by hovering over the 'drag' icon at the left of the version name.
 Release a version
1. On the 'Versions' page, hover over the relevant version to display the cog icon, then select Release from the drop-down menu.
2. If there are any issues set with this version as their 'Fix For' version, Jira allows you to choose to change the 'Fix For' version if you wish.
Otherwise, the operation will complete without modifying these issues.

To revert the release of a version, simply select Unrelease from the drop-down menu.

Archive a version
1. On the 'Versions' page, hover over the relevant version to display the cog icon, then select Archive from the drop-down menu.
2. The version list indicates the version 'archived' status with a semi-transparent icon. No further changes can be made to this version unless it is
un-archived. Also it is not possible to remove any existing archived versions from an issue's affected and fix version fields or add any new
archived versions.

To revert the archive of a version, simply select Unarchive from the drop-down menu.

Delete a version
1. On the 'Versions' page, hover over the relevant version to display the cog icon, then select Delete from the drop-down menu.
2. This will bring you to the 'Delete Version: <Version>' confirmation page. From here, you can specify the actions to be taken for issues
associated with the version to be deleted. You can either associate these issues with another version, or simply remove references to the
version to be deleted.

Merge multiple versions

Merging multiple versions allows you to move the issues from one or more versions to another version.
1. On the 'Versions' page, click the Merge link at the top right of the page.
2. The 'Merge Versions' popup will be displayed. On this page are two select lists both listing all un-archived versions.
In the 'Merging From Versions' select list, choose the version(s) whose issues you wish to move. Versions selected on this list will be removed
from the system. All issues associated with these versions will be updated to reflect the new version selected in the 'Merge To Version' select
list. It is only possible to select one version to merge to.
3. Click the Merge button. If you are shown a confirmation page, click Merge again to complete the operation.

Reschedule a version
Recheduling a version changes its place in the order of versions.

On the 'Versions' page, click the icon for the relevant version, and drag it to its new position in the version order.

Last modified on Sep 12, 2017

Was this helpful?
Yes

No

Provide feedback about this article

Related content

Configuring versions in a Scrum project

Configuring versions in a Kanban project

Version Report

Releasing a version

Deploying a release
 Reporting

Not finding the help you need?

Ask the community

Planning a version
In this section

Configuring versions in a Scrum project

Configuring versions in a Kanban project

Working with epics

Related content

Getting to work

Starting a new project

Organizing work with versions

Configuring development tools

Releasing a version

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.
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 versionshelps 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 sprintsto 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 to 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 Aug 7, 2017
 Was this helpful?
Yes

No

Provide feedback about this article

In this section

Configuring versions in a Scrum project

Configuring versions in a Kanban project

Working with epics

Related content

Getting to work

Starting a new project

Organizing work with versions

Configuring development tools

Releasing a version

Not finding the help you need?

Getting to work
In this section
 Running sprints in a Scrum project

Checking the progress of a version

Monitoring work in a Kanban project

Related content

Building a backlog

What is a board?

Starting a new project

Completing a sprint

Planning sprints

Reporting

Ready to start working? You should have built a backlog and planned your version and epics by this stage. Time to get your team
working!

The documentation in this section will help you use Jira Software to coordinate your team's work. For Scrum, these tasks
include planning and running sprints. For Kanban, these tasks include monitoring work in progress. Both Scrum and Kanban use
boards (Active sprints/Kanban board) and wallboards to keep your team on track.

Working in a Scrum project

Scrum projects are based around working in sprints. A sprint is an iteration of work (two to four weeks) that is typically part of a
version. Each sprint starts with a planning meeting where the work is estimated and assigned to the sprint. At the end of each sprint, a
retrospective or review meeting is held before the next sprint is planned.
In Jira Software, sprints are planned using the Backlog of a board. Once a sprint has started, the sprint is monitored using the Active
sprints of a board.
 Learn more: Running sprints in a Scrum project, Checking the progress of a version, and Using Active sprints
Working in a Kanban project
Unlike Scrum, Kanban doesn't use the concept of sprints. Rather, a Kanban project is based on the continuous delivery of work. When
tasks are completed, more tasks are pulled into the work-in-progress pipeline. Constraints are placed on the amount of work that can
be done at one time, so that the team is not overburdened.
In Jira Software, work is managed and monitored using the Kanban board.
Learn more: Monitoring work in a Kanban project and Using your Kanban backlog

Already finished work for the version?

Next: Release your version
Project lifecycle
NEW PROJECT BACKLOG NEW VERSION WORK RELEASE REPORTING
Last modified on Oct 10, 2017

Was this helpful?

Yes

No

Provide feedback about this article

In this section

Running sprints in a Scrum project

Checking the progress of a version

Monitoring work in a Kanban project

Related co
 Releasing a version
In this section

Checking the release status of a version

Deploying a release

Related content

Checking the progress of a version

Configuring versions in a Kanban project

Organizing work with versions

Running a Bamboo build when releasing a version

Configuring versions in a Scrum project

Using the release page to check the progress of a version

Releasing a version is the culmination of your team's hard work. It may be the result of many iterations of work across a number of
months. As the iteration manager, it will be your job to ensure that all the work is complete for the release, and to coordinate the
activities needed to release the version.

As described in Configuring versions in a Scrum project and Configuring versions in a Kanban project, versions are handled
differently in Scrum and Kanban projects. A version in a Scrum project is pre-planned and is released when the planned work is
complete. In a Kanban project, a version can be released at any time the version will contain all issues that are complete at that
time.
Check the release status
of a version
Before you release a version, you need to be sure that everything is ready issues are complete, code is committed, reviewed and
merged, builds are passing, etc. In Jira Software, the Release Hub can provide you with the information you need for a release, in one
place.
Learn more: Checking the release status of a version
Deploy the release
Deploying your release requires actions to be taken on a number of different systems. The version in Jira Software needs to be
released, build(s) need to be run to generate the artifact, the artifact needs to be deployed to the right environments, etc.
Learn more: Deploying a release
Create the release documentation
Once you have deployed your release, you may want to create documentation to accompany it. If you have Jira Software connected to
Confluence, you can generate a 'Change Log' report in Confluence for your stakeholders.
Learn more: Jira Report Blueprint

Already released your version?

Next: Reporting
Project lifecycle
NEW PROJECT BACKLOG NEW VERSION WORK RELEASE REPORTING
Last modified on Oct 10, 2017

Was this helpful?

Yes

No
 Provide feedback about this article

In this section

Reporting
In this section

Burndown Chart

Control Chart

Cumulative Flow Diagram

Epic Burndown

Epic Report

Release Burndown

Sprint Report

Velocity Chart

Version Report

Related content

Checking the progress of a version

Using your Scrum backlog

Getting to work

Configuring versions in a Scrum project

 Organizing work with versions

Estimating an issue

Reporting is an activity that you will be doing throughout a project. Jira Software has a range of reports that you can use to show
information about your project, versions, epics, sprints, and issues.

The documentation in this section will help you configure and use the reports in Jira Software.

Generating a report
1. Navigate to the desired board and click Reports. The last report viewed will be displayed.
2. Click Switch report to view a different report. The reports in this list are specific to agile development.
See the 'Reports for Scrum projects' or 'Reports for Kanban projects' sections below for more details.
3. If you want to view reports that are not specific to agile development, select All reports from the Switch report drop-down, and view the reports
that are not in the 'Agile' section. See the 'General reports for analyzing issues' section below for more details.

Reports for Scrum projects

Chart Applies to Purpose

Tracks the total work remaining, and projects the

likelihood of achieving the sprint goal.
Burndown Chart Sprints
This helps your team manage its progress and respond
accordingly.
 Shows the work completed or pushed back to the
Sprint Report Sprints backlog in each sprint.
This helps you determine if your team is
overcommitting or if there is scope creep.

Control Projects, Shows the cycle time for your product, version, or
ChartControl versions, or sprint.
Chart sprints This helps you identify whether data from the current
process can be used to determine future performance.

Cumulative Flow Any period of Shows the statuses of issues over time.
Diagram time This helps you identify potential bottlenecks that need
to be investigated.

Shows the progress towards completing an epic over

time.
Epic Report Epics
This helps you manage your team's progress by
tracking the remaining incomplete and unestimated
work.

Similar to the Epic Report, but optimized for Scrum

teams that work in sprints. Tracks the projected
Epic Burndown Epics number of sprints required to complete the epic.
This helps you monitor whether the epic will release
on time, so you can take action if work is falling
behind.
 Similar to the Version Report, but optimized for Scrum
Release teams that work in sprints.
Versions
Burndown Tracks the projected release date for a version. This
helps you monitor whether the version will release on
time, so you can take action if work is falling behind.

Tracks the amount of work completed from sprint to

sprint.
Velocity Chart Sprints
This helps you determine your team's velocity, and
estimate the work your team can realistically achieve
in future sprints.

Tracks the projected release date for a version.

Version Report Versions This helps you monitor whether the version will
release on time, so you can take action if work is
falling behind.

Reports for Kanban projects

Chart Applies to Purpose

Shows the cycle time for your product, version, or sprint.

Control Chart Projects, versions, or sprints
This helps you identify whether data from the current process can be used to
determine future performance.

Cumulative Flow Any period of time

Shows the statuses of issues over time.
Diagram
This helps you identify potential bottlenecks that need to be investigated.

Chart Purpose

Average Age Shows the average age of unresolved issues for a project or filter. This helps you see whether your backlog is being kept up to
Report date.

Maps created issues versus resolved issues over a period of time. This helps you understand whether your overall
Created vs backlog is growing or shrinking.
Notes...
Resolved Issues
Report

Shows a pie chart of issues for a project or filter grouped by a specified field. This helps you see the breakdown of a
Pie Chart Report set of issues, at a glance.
For example, you could create a chart to show issues grouped by Assignee for a particular version in a project (using a
filter).

Shows the number of issues created over a period of time for a project or filter, and how many were resolved. This
helps you understand if your team is keeping up with incoming work.
Recently Created Notes...
Issues Report

Resolution Time Shows the length of time taken to resolve a set of issues for a project or filter. This helps you identify trends and incidents that
Report you can investigate further.

Single Level Shows issues grouped by a particular field for a filter. This helps you group search results by a field, and see the
overall status of each group. For example, you could view the issues in a version of a project, grouped by Assignee.
Group By Report
Note that there is a display limit of 1,000 issues for this report.

Time Since Issues For a date field and project or filter, maps the issues against the date that the field was set. This can help you track how many
Report issues were created, updated, etc over a period of time.

Shows time tracking information on issues for a particular version of a project.

Notes...

o
o
o
Time Tracking o
Report *

1.
 2.

3.

Note that this report can only display up to 1,000 issues and 1,000 sub-tasks.

User Workload Shows how much work a user has been allocated, and how long it should take.
Report * For a specified user, you'll be able to see the number of unresolved issues assigned to the specified user, and
the remaining workload, on a per-project basis.

Version Shows how much outstanding work there is (per user and per issue) before a given version is complete.
Workload
Report * For the specified version, you'll be able to see a list of unresolved issues assigned to each user, each user's workload,
and a summary of the total remaining workload for the version.

Workload Pie
Shows the relative workload for assignees of all issues for a project or filter.
Chart Report *

* Only available if your Jira administrator has enabled time tracking.

 Reports available in Confluence
If you have connected Jira to Confluence, you can create the following reports in Confluence:

Chart Purpose

Change Log Displays a list of issues from Jira. This list can be static or dynamic, automatically updating as the status of your issues change in Jira.

Status The Status Report displays the progress of a Jira project and fix version in pie charts by status, priority, component, and issue
Report type. The Status Report uses the Jira Chart macro, and is dynamic.

Other reports
Additional reports (e.g. Gantt Chart Report, Timesheet Report, Jira SQL Plugin) are available for download from the Atlassian Marketplace.
Jira administrators can also create new reports with the plugin API see our Tutorial - Creating a Jira report. If you don't want to build a plugin
yourself, Atlassian Experts are available for custom projects.
Issue filters can be exported to Microsoft Excel, where they can be further manipulated into charts and reports. See Working with search results.

What next?
You are done! Now the cycle begins again. You will probably be planning a new version, even as you wrap up an existing version.
You might even be ready to start a new project. Check out the previous topics below:

Starting a new project

Building a backlog
 Planning a version
Releasing a version

Project lifecycle
NEW PROJECT BACKLOG NEW VERSION WORK RELEASE REPORTING
Last modified on Oct 16, 2017

Was this helpful?

Yes

No

Provide feedback about this article

In this section

Burndown Chart

Control Chart

Cumulative Flow Diagram

Epic Burndown

Epic Report

Release Burndown

Sprint Report

Velocity Chart

Version Report
Relat

https://confluence.atlassian.com/jirasoftwarecloud/leading-agile-projects-764477946.html aici gasesc totul despre Jira si cum se fac proiecte

Agile in Jira

https://www.atlassian.com/git/tutorials/comparing-workflows si aici mai multe de citit