Академический Документы
Профессиональный Документы
Культура Документы
First things first. If you haven't already got the JIRA Agile add-on up and running, carry out the
following steps.
If you are using JIRA Cloud, you can skip this section. JIRA Agile can be added to your
account by configuring your subscription as documented here.
If you are using JIRA 6.3.1 or later, you will have the option of including JIRA Agile when
you install JIRA, as JIRA Agile is bundled with JIRA. If you have done this, you do not need to
install it again. However, you may need need to upgrade it, as the bundled JIRA Agile version
may not be compatible with the JIRA
1.
Log in to JIRA as a user with the 'JIRA System Administrators' global permission.
2.
3.
4.
Click the 'cog' icon on the top bar (or click Administration if using an older version of
JIRA) and select Add-ons. The Universal Plugin Manager (UPM) page will be displayed.
On the Find new add-ons page, type 'JIRA Agile' in the search box.
The JIRA Agile add-on will appear in the list below the search box. Click
the Install button. A confirmation message and the add-on details will display, if it is installed
successfully.
2.
Click the 'cog' icon on the top bar and select Add-ons.
3.
4.
5.
In the 'Filter visible add-ons' box, enter 'jira agile', then expand the 'JIRA Agile' entry in
the filtered results.
Click the pencil icon next to the License Key field to make it editable.
6.
Paste your license into the License Key field and click Update.
You can copy your JIRA Agile license from https://my.atlassian.com, where you can either
generate a new Evaluation License Key, or retrieve your old License Key if you already have
one.
For more information please see Specifying your License Details.
2.
3.
Enter the Username, Password, Full Name and Email Address; and (optionally) tick
the box to send the user an email containing their account details. Then click Add.
For more details, please see the JIRA documentation on Managing Users.
4.
The User Browser will be displayed. Locate the new user and click the Groups link in
the Operations column.
5.
Click the Agile menu in the top navigation bar. The Getting Started page will appear.
2.
If someone has already created a Scrum board for you to use, click Open an
existing board (in step 2).
Otherwise:
If you already have a JIRA project in which to store your Agile tasks,
click create a new Scrum board (in step 2). Otherwise, click create a new project and
board (in step 1). Type a descriptive Name and unique Key for your project, and select
the Project Lead (that is, the person who will manage this project).
Note that you will need the 'Administer Project' permission and the 'JIRA
Administrators' global permission in order to create a JIRA project. If you don't have these
permissions, you will need to ask your JIRA administrator to create a project for you. For more
details, please see the JIRA documentation on Defining a Project.
Enter the name of your new board, and select the project(s) you wish to
work on.
Note that you will need the JIRA 'Create Shared Objects' global permission in order to
create a board.
Select Agile > Manage Boards from the top navigation bar.
On the Manage Boards screen, click the Configure link corresponding to the board of
interest.
3.
On the B oard Configuration screen, click the Estimation and Tracking tab.
4.
In the Time Tracking field, select Remaining Estimate and Time Spent.
... or ...
Getting Started: Kanban
Kanban is often used by bugfix teams who deliver maintenance releases of their product. Kanban
is also well suited to DevOps, Build Engineering and Support teams.
Creating a Kanban Board: (click to expand)
1.
Click the Agile menu in the top navigation bar. The Getting Started page will
appear.
2.
Enter the name of your new board, and select the project(s) you
wish to work on.
Note that you will need the JIRA 'Create Shared Objects' global permission in order to
create a board.
Creating a Board
For more information, please see Creating a Board.
Setting Column Constraints: (click to expand)
Constraints specify how many issues a column can contain. If the constraint for a column is
exceeded, the constraint will be highlighted in red.
To set constraints based on the number of issues in a given column:
1.
2.
Select Agile > Manage Boards from the top navigation bar.
On the Manage Boards screen, click the Configure link corresponding to the board of
interest.
3.
4.
5.
To set the columns Max constraint, click the red box at the top of the column, type the
new value and press the Enter key. E.g. if your business practice is to have no more than 5
issues 'In Progress' at any one time, you would specify 5.
6.
Click the Use Board button (at the top of the page). Your board will refresh with the
column constraint applied. If the total number of issues in that column exceeds the maximum
capacity, the column will be highlighted in red.
4. Ranking Issues
Scrum teams typically try to rank items in their backlog in the order they should be implemented,
starting from the top. Kanban teams (which do not have a backlog) organise their To Do column
in the same way.
To rank (prioritise) issues in your project (click to expand):
In the Backlog (if you are using Scrum):
1.
2.
1.
2.
Click each issue (story) on the left-hand side of the screen to display its details on the
right-hand side of the screen.
3.
Enter an Estimate for each story by clicking the Estimate field on the right-hand side of
the screen. For more information, please see Estimating an Issue.
2.
3.
Your new 'upcoming' sprint will be added to your board, below any other future sprints. If
you wish, you can edit the name, start date and end date.
4.
Drag-and-drop the relevant issues into your new sprint (see Adding an Issue to a Sprint).
5.
6.
Working on Issues
7. Viewing your "To Do" List
To view work-in-progress (click to expand):
1.
2.
To see only the issues that are assigned to you, click the Only My Issues button.
8. Filtering Issues
You can use Quick Filters to filter issues on-the-fly, enabling you for example to only see issues
of a particular type (such as 'Bug').
2.
3.
In the Name field, enter Bugs only (or whatever is appropriate for your needs).
4.
In the JQL field, enter type = bug (or whatever is appropriate for your needs).
5.
6.
Your board will now have a new button for your new Quick Filter.
To move an issue from one column (JIRA status) to the next (click to expand):
1.
2.
Select Active sprints (Scrum) / Kanban board (Kanban) on your preferred board.
Drag and drop the desired card(s) to the column that matches the status to which you
want to assign the issue(s).
If moving an issue causes a constraint to be exceeded, the affected constraint will be
displaed in red (maximum) or yellow (minimum).
1.
2.
Click the cog dropdown, next to the sprint name, to display a dialog box.
3.
If you wish, edit the Sprint Name, Start Date or End Date.
4.
5.
You will be taken to the Sprint Report. Your issues will move out of the Active sprints. Any
incomplete issues will move back into the backlog and will be visible in the Backlog.
In the Completed Issues section of the Sprint Report for your completed sprint,
click View in Issue Navigator.
2.
You can then use JIRA's Bulk Edit to assign all of the issues to the relevant version (for
details, please see the JIRA documentation on Bulk Operations).
... or ...
Releasing a Version (Kanban)
To create and release a new version: (click to expand)
1.
2.
Click the Release link at the top of the Done (rightmost) column.
You will need to have the JIRA 'Project Administrator' permission in the project(s) whose
issues are to be included in the version.
3.
The 'Release' window will display. Enter the Version name and Release date (optional
will default to today's date).
4.
Click the Release button to save your new version and mark it as 'released' throughout
JIRA and JIRA Agile.
Creating a Board
For more information, please see Releasing a Version (Kanban).
2.
Select Burndown Chart from the drop-down at left to display the burndown chart for your
active sprint.
3.
Any changes to scope (e.g. issues added to sprint, issues removed from sprint) are
shown in the table below the graph.
2.
3.
2.
3.
... or ...
Tracking Progress: Kanban
A Cumulative Flow Diagram (CFD) shows your work-in-progress and helps you to identify
bottlenecks in your processes.
To view the CFD: (click to expand)
1.
2.
Select Cumulative Flow Diagram from the drop-down at left to display the CFD.
For more information, please see Viewing the Cumulative Flow Diagram.
A Control Chart shows you the cycle time (or lead time) for your product, version or sprint.
To view the control chart: (click to expand)
1.
2.
Select Control Chart from the drop-down at left to display the control chart.
3.
Hover over the graph at any point to display actual values of the moving average.
Ensure that the JIRA Wallboards add-on has been installed. (This is similar to installing
the JIRA Agile add-on as described above.)
2.
Click the Dashboard menu in the top navigation bar and create a new JIRA
dashboard for your new wallboard.
Since existing dashboards may contain gadgets which are not wallboard-compatible, avoid
copying an existing dashboard.
3.
On your new dashboard, click the Add Gadget link (top right). The Gadgets
Directory will display. Find the JIRA Agile Wallboard Gadget in the list of gadgets and
click Add it now.
4.
5.
Select View as Wallboard from the Tools drop-down on your dashboard and stare in
awe at your fresh new wallboard. For optimal use of screen real-estate, enter full-screen mode
on your browser (F11 in Firefox 3.6 and Chrome 5; Safari requires a plugin to enable fullscreen mode) and refresh the page. Wallboards are optimised for 1920x1080 and 1920x1200
pixel resolution screens, but should also work in some other resolution modes.
For more information, please see the documentation on Using the JIRA Agile Gadgets,
the Wallboards add-on and the JIRA Dashboard.
click 'o' to open the issue which is currently showing in the detail view on a board.
click 'Enter' to submit the content of a field being edited in the detail view on a board.
click 'Shift' + 'Enter' to add a new line to a field being edited in the detail view on a board.
click 's' + 't' to move an issue to the top of the current column on a board. (Only
applicable if Ranking has been enabled.)
click 's' + 'b' to move an issue to the bottom of the current column on a board. (Only
applicable if Ranking has been enabled.)
For more information, please see Using Keyboard Shortcuts.
To go straight to JIRA Agile whenever you log into JIRA: (click to expand)
Advanced Topics
16. Grouping Stories into an Epic (Scrum)
If you have a very large, complex story, you may want to create several smaller stories (issues) to
cover various aspects of the work. You can then collect all these issues together using an epic.
To create an epic (click to expand):
1.
2.
3.
4.
In the Epic Name field, enter a short name. The Epic Name will be used to identify your
epic and the issues that belong to it.
5.
Your new epic will be added to your board's Epics panel. Drag-and-drop the relevant
issues into your new epic (see Adding an Issue to an Epic).
3.
4.
5.
You can optionally specify the version Start Date and planned Release Date.
6.
Your new version will be added to your board's Versions panel. Drag-and-drop the
relevant issues into your new version (see Adding an Issue to a Version).
If you are using Scrum and the issue is currently in the planning phase, click Plan;
otherwise click Work.
2.
Locate the parent issue (story) for your new sub-task, and click its issue key (or type t in
the Active sprints/Kanban board) to display the Issue Detail View on the right-hand side of
the screen
3.
4.
5.
Enter your sub-task's details into the Create Issue dialog box (see Creating an Issue).