Jira Issue Workflow Configuration

Jira Workflow: A Jira workflow is a set of statuses, transitions & triggers that an issue moves through during its lifecycle, and typically represents a process within your organization. Workflows can be associated with particular projects and, optionally, specific issue types by using a workflow scheme.
Workflow can be defined for Story, Task, Bug, Sub-task & epic seperaltely or as a common based on subscription model opted by a user/organization.
It is also referred as "issue workflows" in Jira. Atlassian articel can referred here.

In order to configure a workflow user should first be aware of configured Jira process i.e. is it a company managed or team managed project setting in Jira while initial configuration was done. Note: Project once configured cannot be modified/migrated from team manager to company manager and vice-versa.

Below is the pictorial representation of how a user can identify if the project is company manager or team managed.

Detailed information on this is available here.

Pre-requisute:
  • User should be Jira Admin / Project Admin
  • User should be project member.
Steps on navigating to the Issue workflow in Jira (Team Managed)
  1. Select Project for which workflow needs to be modified.
  2. Navigate to Project Settings on left sidebar.
  3. Navigate and select Issue types from left sidebar.
  4. Select a issue type. e.g. Story.
  5. Select Edit Workflow on top right corner or .
  6. Note: A Standard workflow has ToDo, Inprogress & Done as a status pre-configured.

  7. Admin can add status, standard or custom from the top menu "Add Status" button and "Add transaction" i.e. an action to move the task to next state using button.
  8. Once the workflow and transactions are mapped and finalised user can apply same to project by clicking or .
  9. Note: Workflow status cannot be changed is already in user, in this case user will first need to create a new workflow and need to manually move the Issues to new status and de-activate the old workflow.

    User can also add triggers based on the subscription model to update assignee automatically while transitioning statuses.
    For Company Managed settings arcticle will be updated soon.

Comments

Popular posts from this blog

How to verify systems designed in Business Analyst

Customizations: Oracle SaaS vs PaaS

Certifications and it's details