Bugzilla-like ACK flags necessary for state change - possible in Jira?

[Ondrej Zizka]

In Red Hat Bugzilla, there's a requirement for a bug to have an ACK from multiple parties before it can change to some state (usually 3 - Dev, QA, product management).

Is that achievable in Jira?

[Avdhesh Chauhan · Accepted solution]

Yes, just give an Ack transtion and add a counter in that transtions post function (a simple groovy can do this)

Now based on that u can have the conditions in your sub sequent transtions

[Nic Brough -Adaptavist-]

Transition - the action of moving from one status to another

Post-function - some code you can run at the end of the transition

Counter - not a Jira specific term, Avdhesh simply means "create a numeric field and use a post function to add one to it's value every time you run the transition"

Oh, and "groovy" is mentioned - this is from a an addon which provides a framework for scripting some functions inside Jira

Have a look at https://confluence.atlassian.com/display/JIRA/Configuring+Workflow to begin with

[Ondrej Zizka]

I am new to this, so terms like transition, counter, post function are a bit unclear to me. Could you please point me to some docs or howto such? Thanks.

[Ondrej Zizka]

Great, thanks! I thought it would be as you wrote, just wasn't sure if it would force certain order of ACKs. But overall, if it's scriptable, then I guess I'd figure out something.