Typical Project flow with QA Loop in Jira (Atlassian)

Last week, one of my friend needs some help to establish Project\QA workflows on Jira (Atlassian)
So here I am happy to share some of my odd solution.

Project Flow problems or hard to implement in Jira were

* One stage splits with multiple stages in flow.
* More than one stages merges to one stage.

Here We have Brainstorming splits to UT - ST stage and Dev Review - QA Review merges with Review stage executed by System Group Members in project flow.

One issue splits with more than one issues, can also be implemented with sub-tasks feature but it may not push next stage in the project flow as the project progresses; all sub-tasks are linked to the parent task only, may not execute inline flow; may not give more control to administrator\lead and may be more complicated to maintain. Sub-tasks may not be merged to one task on transitions after Dev. Review / QA Review merges to Review stage.

Core objective is to implement flow that anyone can see each stage of the flow and can go back and forth from any stage, Dev and QA stage should work parallel and merge to "Review" and then System Verification should be executed as build in QA loop.
Administrator \ Lead of each stage would have full control to execute project development and would have transparency; Jira could help to push next stage after each stage done.

We first implement above flow as manually after we will find which actions need to automate.
Manually Implementation :
# Created issue types for all Project Concept, Brainstorming, ST Identification, UT Identification...until System Verification as Standard Issue type like task.
# Create work-flow schemes for each issue type we have created i.e. ProjectConcept work-flow will have step Created, Go for Brainstorming , Reopen.
# Enable Issue Linking from Administrator and create two link type as we have two flow one is task flow other is defect flow.
* Project Flow :
- Outward Description : created after , Inward Description : progressed to
* Defect QA Loop :
- Outward Description : Linked to , Inward Description : Linked by
# Associate each work-flow with its issue type.
# When flow step done -- create new issue type of the next flow step and link it with its previous parent issue type on Project Flow.
# On SV step make it open and add reference to each defect in its sv step.

Here is snapshot after implemented above actions :

We can automate manual actions
# Create next flow issue type when specific issue committed or completed,
# Assign to the lead,
# Add reference(link) to previous parent issue type.
Automation :
Here I will show one implementation from stage Project Concept to Brainstorming; Others can be implemented as same way.
For this we will create Jelly script and add them in Jelly Service of Jira.Script executes filter and get issues with issue-type : Project Concept , status : "Go for brain storming" and which does not have comment "Brainstorm added" and does manual actions and then add comment "Brainstorm added" to project concept(previous step of the flow) so next time when service executes same project concept will not create brainstorm step.
Created filter : GetProjectConceptsWithNonBrainstormingAdded at desk for this project.

Copy script code
To execute above script, update your FilterId with 10020 to yours filterId, to find filterId go to Find Issues / Manage and put cursor on your filter and see the filterId on status bar.

Please, feel free to ask any question regardings.

Thanks,
Nimesh Vadgama.