Scribd
Upload
121 views4 pages

Jira Workflow For Issue Type: Task, Sub-Task, Improvement: To Do On Hold

The document describes Jira workflows for different issue types including tasks, support tickets, stories/epics, and bugs. Each workflow shows the possible statuses an issue can be in and the transitions between statuses. A common element is that setting the status to "Done" or "Close" requires selecting a resolution in a modal window first.

Uploaded by

LadyBrune
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
121 views4 pages

Jira Workflow For Issue Type: Task, Sub-Task, Improvement: To Do On Hold

The document describes Jira workflows for different issue types including tasks, support tickets, stories/epics, and bugs. Each workflow shows the possible statuses an issue can be in and the transitions between statuses. A common element is that setting the status to "Done" or "Close" requires selecting a resolution in a modal window first.

Uploaded by

LadyBrune
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

JIRA WORKFLOW FOR ISSUE TYPE: TASK, SUB-TASK, IMPROVEMENT

All statuses

need information
TO DO ON HOLD

development started

unblocked
DEV IN PROGRESS
code review failed
blocked

development finished

WAITING FOR
QA failed CODE REVIEW

merge on develop for QA

READY FOR QA

Close without
QA started code review

QA IN PROGRESS

QA approved

Kada se postavi status DONE, treba da izadje


All statuses
onaj SET RESOLUTION modal. Znaci bilo koja
DONE tranzicija ka DONE mora da ima taj SET
RESOLUTION modal pre nego sto se konacno
postavi status na DONE
JIRA WORKFLOW FOR ISSUE TYPE: SUPPORT TICKET

All statuses

OPEN
more information needed

resolving started

not resolved need info


RESOLVING IN
provided info ON HOLD
PROGRESS

request confirmation Resolved


from support

All statuses
WAITING FOR
confirmed by
SUPPORT CLOSE A
support
CONFIRMATION

Kada se postavi status CLOSE, treba da izadje


onaj SET RESOLUTION modal. Znaci bilo koja
tranzicija ka CLOSE mora da ima taj SET
RESOLUTION modal pre nego sto se konacno
postavi status na CLOSE
JIRA WORKFLOW FOR ISSUE TYPE: STORY, EPIC

All statuses

TO DO information needed

development started

blocked
IN PROGRESS ON HOLD
unblocked

not accepted finished

WAITING FOR PM
APPROVAL

accepted by PM

All statuses

DONE A

Kada se postavi status DONE, treba da izadje


onaj SET RESOLUTION modal. Znaci bilo koja
tranzicija ka DONE mora da ima taj SET
RESOLUTION modal pre nego sto se konacno
postavi status na DONE.
JIRA WORKFLOW FOR ISSUE TYPE: BUG

All statuses

OPEN
more information needed

resolving started

need info
RESOLVING IN
ON HOLD
PROGRESS
provided info

not resolved
Send to QA  Resolved
confirmation

All statuses

READY FOR QA CLOSE A

QA started

Kada se postavi status CLOSE, treba da izadje


onaj SET RESOLUTION modal. Znaci bilo koja
tranzicija ka CLOSE mora da ima taj SET
QA IN PROGRESS confirmed by QA RESOLUTION modal pre nego sto se konacno
postavi status na CLOSE

You might also like