It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Adding Approvers to Issue workflow - Jira (online)

Vlad Diary Sep 08, 2012

I am trying to use Jira (online) as a Change Control Request system. Here is the workflow process that I'm trying to achieve:

Step 1 - A defect is identified. A team member creates and submits the issue in Jira (online). The issue at this point is in Pending Approval status.

Step 2 - I need to have two levels of approvals applied (from a pool of approvers - order of approval is not important). Once approved, the issue status is changed to Approved and it becomes visible to the Developers

Step 3 - Developers address the issue and complete the Jira request - status changed to "Completed"

Step 4 - The project team runs a report on Completed items/issues and confirms defect fix by closing the issue - status changed to "Closed"

Can someone please guide me on how to set it up.

Thank You,

Vlad

4 answers

2 votes
Norman Abramovitz Sep 11, 2012

Ok, Since you are using the OnDemand system, I would either create a project role or a group with the three people in the group or has the project role. You cannot do it without the new states since you cannot add any plugins.

Then I would extend your workflow to add two new states to correspond to the two approvals. Lets call those states Approval_1 and Approval_2. Since the approvals have no ordering, I would add a two fields to represent which approval is being given. I would use one of the following conditions

User Is In Group

User Is In Group Custom Field (another field added to the screen if all you really about is the person giving the approval verses the type of approval. I this case the two field is the list of users that can give approval.)

or User Is In Project Role

On each of the new states would restrict the transition to those approval people based upon the group or project role.

0 votes
Norman Abramovitz Sep 08, 2012

What you want to do is of course possible. We need more information about the two level approval. Is it a group of people or a single person that does the approval? Is there an order to the two level approval? Is there any problem creating a separate state for each approval level?

My suggestion is the developer does not close issue, but the person that comfirms the issue actually closes the issue with his/her comments.

Is this Jira system an OnDemand type?

0 votes
Vlad Diary Sep 10, 2012

There is a total of 3 people who can approve, any combination of two is accepted - order not important. Using the online version.. (not the downloaded client)

And you're right, the developer should not close the issue - I meant to say mark it "Completed"

P.S. I've updated my original question to reflect your comments

0 votes
Vlad Diary Sep 10, 2012

there is a total of 3 people who can approve, any combination of two is accepted - order not important

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Published in Next-gen

Introducing subtasks for breaking down work in next-gen projects

Teams break work down in order to help simplify complex tasks. This is often done iteratively, with tasks being broken down into smaller tasks and so on until the work is accurately captured in well-...

923 views 12 15
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you