Creating an agile project from a "template" in jira

jira-agile-setup.md

Setting up a new Agile Scrum project in Jira

1. create new project
2. choose "scrum software development"
3. click 'select' on the next screen to use the default issue type for now
4. choose a name and project lead
5. go to 'project administration' (this option is in different places depending on your view)
6. you should be viewing the summary now. do these:
   1. issue types
      • under "Issue Types", click the scheme name, which is a blue link.
      • in the "Actions" button, click 'use a different scheme'
      • select "Choose a scheme the same as an existing project" radio button
      • in the "Project" dropdown, select "Template Project Config", click OK.
      • go back to summary
   2. workflow
      • under "Workflows", click the scheme name, which is a blue link.
      • click "Switch Scheme" button
      • choose "Agile staging/prod Workflow Scheme"
      • click "Associate" and then again on the next page
      • go back to summary
   3. screens
      • under "Screens", click the scheme name, which is a blue link.
      • in the "Actions" button, click 'use a different scheme'
      • choose "Agile Simple Issue Tracking Issue Type Screen Scheme (use with agile workflow)"
      • click "Associate"
7. click "Back to Project". if you're not already in the "Board" view, click "Boards" and choose this project's board.
8. configure the board:
   1. click "Board" on the right, choose "Configure"
   2. click "Columns" on the left
   3. using the 'Add column' button and by dragging statuses around, make sure you have these columns with these statuses inside them:
      • Unmapped Statuses
        • closed
      • Backlog
        • backlog
      • To Do
        • selected for development
        • review rejected
        • reopened
      • In Progress
        • in progress
        • development complete
      • Ready for QA
        • under review on internal staging
        • on client staging
      • Accepted
        • internally accepted
        • client approved
      • Done and Live
        • live
   4. click "Estimation" on the left
      • change "Estimation Statistic" to "Original Time Estimate"
      • change "Time Tracking" to "None"
   5. Alternatively, you can use the "Remaining Estimate and Time Spent" time tracking, which is more flexible throughout the sprint and will likely result in better burndown charts and time tracking, but requires much more micro-management of remaining time estimates on issues.
9. feel free to use the "Current Sprint" dashboard that i've created and shared globally.

you basically want to be in the "Board" view at all times, with the "Active Sprint" and "Reports" (switched to 'burndown chart') tabs being the most useful. I use the "Backlog" tab to create sprints, add time estimates and get a lay of the land for the near future.

gotchas:

• when creating a sprint, you must add the time estimate to issues before adding them to the sprint.