JIRA Workflows: Convert tasks into systematic and transparent procedures

If measures for quality assurance and both internal and customer projects don’t run ideally and thus inefficiently, it is often due to a lack of established and binding workflows in task management. This article focuses on the use of JIRA and shows how JIRA can be used to convert all kinds of tasks into systematic and transparent procedures with the help of prototypical workflows. //SEIBERT/MEDIA is happy to provide you a JIRA test instance free of charge and without commitment, so you can learn about the following workflows and the diverse functions of JIRA.

Minimal Workflow

minimal_workflow-2

Use cases:

  • small projects without release-planning
  • internal organization
  • maintenance and care
  • bugfixing

Features:

  • optional estimation
  • assignee has to be ascribed
  • no quality assurance
  • no internal approval
  • no customer approval

Workflow with quality assurance

workflow_with_quality_assurance

Use cases:

  • small projects without release-planning
  • maintenance and care
  • bugfixing

Features:

  • optional estimation
  • assignee has to be ascribed
  • quality assurance
  • no internal approval
  • no customer approval

Workflow with quality assurance and cost estimation

workflow_with_quality_assurance_and_cost_estimate

Use cases:

  • small projects without release-planning
  • internal distribution of tasks
  • maintenance and care
  • bugfixing

Features:

  • estimation is required
  • assignee has to be ascribed in the step “assign issue”
  • quality assurance
  • no internal approval
  • no customer approval

Workflow with quality assurance, cost estimation and approval

workflow_with_qa_cost_estimate_authorisationb

Use cases:

  • projects with release-planning
  • internal projects with budget control

Features:

  • estimation is required
  • assignee has to be ascribed
  • quality assurance
  • internal approval
  • no customer approval

Workflow with double quality assurance, cost estimation and approval

workflow_with_2x_qa_cost_estimate_authorisation

Use cases:

  • projects with release-planning
  • internal projects with budget control
  • change management of fixed price projects

Procedure:

  1. The request for amendment has to be entered via the interface or sent via e-mail.
  2. The issue is analysed and estimated. You approve the issue as client.
  3. We ascribe the issue to an assignee and handle it.
  4. The results are checked and approved by our staff responsible for QA.
  5. You authorize the successful modification.
  6. The issue is done and gets invoiced.

With the help of these workflows, it is possible to convert internal and external tasks from bug fixing to complex work into standard procedures. The task management with JIRA ensures not only transparency and status visibility but also contributes to the efficient coordination of customer projects and the creation of quality assured results.

2014-09-19_1922

Download Download (1,1 MB): Our wiki brochure in English (PDF)

Share article:Share on FacebookTweet about this on TwitterShare on Google+Share on LinkedInEmail this to someonePrint this page