I have a situation here
Normal Flow --------------------- Dev-Requestor-Close
Another flow is ------------------ Dev-Requestor-QA-Close.
Want some way to implement this based on if a checkbox is checked for QA and accordingly follow the route.
Any help appreciated.
I was able to get around this.
Using Script Runner plugin from JIRA Marketplace.
First, created a field called QA testing Required with 2 values 'Yes' and 'No'.
I create 2 transitions by the same name so as not to confuse the user.
1. Script workflow function : Simple scripted condition : Checks script:
cfValues['QA Testing Required']*.value.contains('Yes')
This is now flowing to the QA person.
2. Script workflow function : Simple scripted condition : Checks script:
cfValues['QA Testing Required']*.value.contains('No')
This skips the QA and follows to the last step.
What I essential did in my solution was to create a dropdown field with 2 values 'yes' and 'no'
I made 2 transitions named 'Ready to Test'. One of them ended up with the QA person if the feild was set to YES and if no the issue flowed directly to the end user for testing.
To accomplish the above i.e. which route to take I installed 'Script Runner plugin'.
Then in the workflow. Go to each transition and perform below steps
I used value.contains as its a drop-down value.
Should be pretty simple once this goes fine.
At the time when this solution was implemented I didn't have that option of Condition+ Value Field. I use the value field now and depending on the field value appropriate transition is displayed. In order to have the user unaware I name both transitions as exactly same so the user clicks on the same button for either flow.
I wanted my user to be unaware of the difference in transition. So when my approver clicks on that 'Ready to Test', he is not aware which flow would be taken up. That decision is through the condition field. If YES, the next step is 'In QA' and If NO, it skips QA and goes directly to the UAT part. makes sense?
I do get what you are saying but in my case there is a field called 'Set for QA Testing'. Now this feild can have a 'YES' or 'NO' value.
If its YES, I want the flow to be
DEV > Requestor > QA > CLOSE
But if the value of this field is NO, the flow would be
DEV > Requestor > CLOSE.
Does this explain clearly?
Well, it all depends on your target. In our case we have 5 possible transitions depending on a certain value in a certain custom field (which is a result of a multiplication during the previous transition). We thought about embedding a Groovy or Pyton script. But one condition for every single transition out of those 5 transitions is the most elegant solution. If the conditions is untrue the transition will be hidden. And it's far less effort compared to a script that has to be written before. Thank you Candy, you made my day!
A bit of a hack I was able to get working, was to use the free Automation add-on; https://marketplace.atlassian.com/plugins/com.atlassian.plugin.automation.jira-automation-plugin/server/overview.
By setting up a rule which fires a cron every minute, runs JQL to find issues where my custom field = x, and takes Transition Action to the desired status. It is not instant, but it met our needs and so far works great.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot