Process management

The process management project template sets you up with a workflow suitable for running most business processes.

The workflow includes review and approval steps, and multiple resolution possibilities.

Use this project type for...

  • Any activities that follow the same steps every time, such as a purchasing process
  • A creative design or content development process
  • Any process where reviews and approvals are mandatory.

Manage activity on the board

Use the Jira Core board to quickly see where your process is at, such as how much work is in progress, or how many items are stuck in review. It also gives you a quick view of what is overdue (if you are using due dates) and who is assigned to issues, so you can follow up.

See Working with boards

Create sub-tasks

If a task that you add is actually a group of smaller tasks, you can create sub-tasks and assign them to different people. The task won't be able to move to "Done" until all the subtasks are complete as well. Sub-tasks don't appear on the board, but are listed on the issues they belong to.

See Creating issues and sub-tasks

Customize issues

The table below shows the specifications for default issues in a process project. If you're a Jira Core admin, you can customize these defaults. For example, you can add other issue types to the project, or add new fields to this issue type. See Configuring your issues.

Issue types Task and sub-task
Issue fields Summary, Issue Type, Reporter, Attachment, Due Date, Original Estimate, Remaining Estimate, Description, Assignee, Priority, Resolution and Labels
Resolutions Done, Won't Do, Duplicate and Cannot Reproduce
Priorities Highest, High, Medium, Low and Lowest

Example use of a process management project

Scenario The department needs a new photocopier and a business case for the purchase needs to be submitted.

Issue lifecycle
  1. Create an issue for the business case.
  2. Start work and move the business case to 'In progress'. Add all the business case details to the issue, including supporting documents (this might include quotes), images, spreadsheets, etc.
  3. When the case is ready for submission, move it to the 'Review' stage and assign to a manager for approval.
  4. Once approved, create a purchase request and send it to the relevant department.
  5. Move the issue to 'Done'.
Issue details
Key actions
  • Re-assign the task to the approver when it gets moved it to review (this can be automated)
  • Leave a comment @mentioning the approver if you need to follow up
  • Set reminders to notify the approver of due dates, if it is time critical
  • Attach any relevant documents, such as quotes or budgets
Last modified on Jun 19, 2018

Was this helpful?

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