JIRA Agile - JIRA Configuration

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

Database tables

When you install the JIRA Agile add-on into your JIRA instance, the following additional tables will be created in your JIRA database to store rank, configuration and sprint information:

  • 'AO_60DB71_COLUMN'
  • 'AO_60DB71_COLUMNSTATUS'
  • 'AO_60DB71_ESTIMATESTATISTIC'  (added around 5.9.5)
  • 'AO_60DB71_ISSUERANKING'
  • 'AO_60DB71_ISSUERANKINGLOG'
  • 'AO_60DB71_QUICKFILTER'
  • 'AO_60DB71_RANK_ISSUE_LINK'
  • 'AO_60DB71_RAPIDVIEW'
  • 'AO_60DB71_SPRINT'
  • 'AO_60DB71_STATSFIELD'
  • 'AO_60DB71_SUBQUERY'
  • 'AO_60DB71_SWIMLANE'
  • 'AO_60DB71_TRACKINGSTATISTIC'

On this page:

Related pages:

Custom fields

If required, JIRA Agile will create the following JIRA custom fields:

Custom fieldTypeNotes
Business ValueThis field is of type 'Number Field' and is available to issue types 'Story' and 'Epic'. (If you want to make it available to other issue types, edit the custom field context.) 
Epic ColourThis field is of type 'Colour of Epic' (which is a field type created by JIRA Agile) and is available to the Epic issue type.

Epic Colour is the colour assigned to the epic. This is auto-assigned initially then can be changed via a dropdown on the colour box on the epic.

(info) This field is not configurable via the JIRA custom fields administration screens.

Epic NameThis field is of type 'Label of Epic' (which is a field type created by JIRA Agile) and is available to the Epic issue type.

Epic Name (editable) is a short name that is used to identify an epic (see Creating an Epic).

(info) This field is not configurable via the JIRA custom fields administration screens.

Epic LinkThis field is of type 'Epic Link Relationship' (which is a field type created by JIRA Agile) and is available to all issue types.

Epic Link is used to determine the parent epic for an issue. This is a non-editable field; it is set by JIRA Agile when you add/remove an issue to/from an epic.

Searchable via JQL.

(info) This field is not configurable via the JIRA custom fields administration screens.

Epic StatusThis field is of type 'Status of Epic' (which is a field type created by JIRA Agile) and is available to the Epic issue type.

Epic Status is used to exclude completed epics from being displayed in the Backlog.

The Epic Status field can have one of the following values:
'ToDo' - indicates that the epic is currently open. The epic will be visible in the board.
'In Progress' - reserved for future enhancements (not used at present).
'Done' - indicates that the epic is completed. The epic will not appear in the board.

(info) This field is not configurable via the JIRA custom fields administration screens.

FlaggedThis field is of type 'Multi Checkboxes' and is available to all issue types.

See Flagging an Issue.

RankThis field is of type 'Global Rank' and is available to all issue types.

See also Enabling Ranking.

Please ensure that your JIRA instance contains only one custom field called Rank, and that the Rank field is assigned to the global context (i.e. not to specific issues or projects).

(info) This field is not configurable via the JIRA custom fields administration screens.

SprintThis field is of type 'Sprint' and is available to all issue types.

Searchable via JQL.

(info) This field is not configurable via the JIRA custom fields administration screens.

Story Points

This field is of type 'Number' and is available to issue types 'Story' and 'Epic'.

  • By default, the Story Points field is only available to issues of type 'Story' or 'Epic' (not 'Bugs' etc) — you can change this by:
    • Associating the Story Points field with other issue types (see the JIRA custom field context documentation).
    • Specifying which screens the Story Points field will be displayed on (see the JIRA documentation on Defining a Screen).

Issue types

When the first JIRA Agile project (Scrum or Kanban) is created in JIRA, JIRA Agile will create the following three JIRA issue types and associate them with the Default Issue Type Scheme:

  • 'Epic'
  • 'Story'
  • 'Technical Task' (sub-task)

Issue type scheme

When the first JIRA Agile project (Scrum or Kanban) is created in JIRA, JIRA Agile will create a new issue type scheme called 'JIRA Agile Scrum Issue Type Scheme' which contains the following issue types:

  • 'Bug'
  • 'Epic'
  • 'Improvement'
  • 'Story'
  • 'Technical Task' (sub-task)

You can add more issue types to this issue type scheme if you wish (provided you have 'JIRA Administrators' global permission).

Workflow

If you choose to create a new project when creating a board via the 'Getting Started' page, JIRA Agile will give you the option of creating a new workflow called 'Simplified Workflow for Project XXX' (see Configuring Workflow), and a workflow scheme called 'Simplified Workflow Scheme for Project XXX' for your new project. This scheme is associated with all issue types.  

Note that this workflow's steps can be edited in JIRA Agile (by project administrators) via a board's Columns configuration page. For more information please see Using JIRA Agile Simplified Workflow.

Simplified WorkflowJIRA Workflow
  • Has three default steps for Scrum boards: To Do, In Progress, Done.
  • Has four default steps for Kanban boards: Backlog, Selected for Development, In Progress, Done.
  • Has more steps than are typically needed on a board (e.g. see the default JIRA workflow).
  • Allows issues to be dragged freely between columns.
  • Has workflow "conditions" which prevent issues from being dragged freely between all columns.
  • Displays no screens on any transitions – all transitions will happen instantly.
  • Automatically sets a resolution of 'Done' when issues are transitioned to the 'successful' column, i.e. statuses mapped to the successful column (see Configuring Columns).
  • Displays screens for Resolve Issue, Close Issue and Reopen Issue.
  • Can be edited from within JIRA Agile (see Adding a new status on the Configuring Columns page), provided you have the 'Administer Projects' permission (for the one project that is on the board).

Permissions

Many JIRA Agile actions depend on a particular JIRA permission:

FeatureScreenActionPermission LevelNotes
SprintsBacklogMove sprint markerProject Admin permission (for all projects in the backlog) 
SprintsBacklogMove issue (reorder/rank)Schedule Issues permission and Edit Issues permissionNot required if you only move issues across the sprint footer without changing the order of the issues
SprintsBacklogStart sprintProject Admin permission (for all projects where an issue is in the selection)Similar permission to creating a Version. Board ownership does not play a role here.
SprintsBacklogCreate sprint

Project Admin permission:

  • For all projects in JIRA if board does not query specific projects; or
  • For all projects queried by the board
 
SprintsBacklogDelete sprint

Project Admin permission:

  • For all projects in JIRA if board does not query specific projects; or
  • For all projects queried by the board
 
SprintsBacklog & Active sprintsAdd issue to sprintSchedule Issues permission and Edit Issues permission 
SprintsBacklogEdit sprint informationProject Admin permission (for all issues in the sprint)Can only be done from the Backlog.
SprintsBacklogReorder sprintProject Admin permission (for all issues in the sprint) 
SprintsActive sprintsComplete sprintJIRA Administrator or Project Admin for all issues in the sprintCan only be done from the Active sprints.
SprintsActive sprintsRemove issue from sprintSchedule Issues permission and Edit Issues permission 
EpicsBacklogCreate epicCreate Issues permission
 
EpicsBacklogRename epicEdit Issues permission
 
EpicsBacklog

Rank epic

Schedule Issues permission 
EpicsBacklogAdd issue to epicEdit Issues permission
 
EpicsBacklogRemove issue from epicEdit Issues permission
 
VersionsBacklogCreate versionProject Admin permission, or JIRA Admin permission(Versions launched out of Labe in 6.2)
VersionsBacklogEdit versionProject Admin permission, or JIRA Admin permission 
VersionsBacklogAdd issue to versionEdit Issues permission 
VersionsBacklogRemove issue from versionEdit Issues permission
 
ConfigConfigureSimplify workflowAdministrator permissionThe board must meet other criteria as well (see Simplified Workflow)
ConfigConfigureAdd statusProject Admin permission (for the one project that is on the board)Project must be currently using an Agile Simplified Workflow
ConfigConfigureRemove statusProject Admin permission (for the one project that is on the board)Project must be currently using an Agile Simplified Workflow
Config Create boardCreate Shared Objects global permission

People without this permission can still create boards but they will not be visible to other users of the system because their filter will not be shared.

Doesn't currently apply to Copy Board.

 

 

Sample data

On the JIRA Agile "Getting Started" page you have the option of importing sample data. If you choose to do this, JIRA Agile will:

  • Update the JIRA Importers add-on.
  • Import two sample projects, called "Scrum Sample" and "Kanban Sample" (you can rename these if you choose), and their issues.
  • Create a "Simplified Workflow" and a "Simplified Workflow Scheme" (see above) for each of these projects.

You may want to delete these projects, and their workflows and workflow schemes, at a later date. You can also use these scripts to import similar sample data later on.

Last modified on Jul 10, 2015

Was this helpful?

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