I am trying to stream line our workflow. We have our process built with a QA status and user acceptance status before being done. I have added the field UAT required (Y/N).
If the answer is Y then I want the status after QA to be User Acceptance.
If the answer is N then the status after QA should be Ready to Release.
Anyone have suggestions on how to make this work?
Hi Raoul,
You can create two transitions leaving the QA status - one to User Acceptance and one to Ready to Release.
Then put a condition on each transition that checks the value of the UAT field.
I was already doing this out of user acceptance. All this did was move the controls "PASS" and "SKIP" into our QA departments hand instead of the UAT teams. Is there a way to automate it so that there is just 1 transition that decides which status to go to depending on the field.
I tried Jira automation and that did not work for me. It could not pick up transitions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So when the QA analyst updates a custom field to say PASS or SKIP (is it a field or a transition to a status?) if the UAT required field says Yes, then you want to auto transition the card to User Acceptance status. Otherwise it should auto transition to Ready to Release.
Is that that scenario? If so, you can easily do that in Automation For Jira. If that is indeed the situation, can you share a screenshot of what you have created in Automation that is not working for you?
If that is not the case, can you give me more insight into the process?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Close. I want the QA analyst to have only 1 button, Pass. Then based on the custom field UAT = No. I want it to transition to the new status of Ready to Release.
If UAT = Yes I want it to transition to the status of User Acceptance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is a very clunky approach, and there's a far nicer one for the end-user.
Set up two transitions from QA, one to User Acceptance and one to Ready to release. Instead of asking someone to fill in a field, just ask them to use the right transition. If you need the field for reporting purposes, then by all means have the field, but set it to "pass" with a post-function when they use one of the transitions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Raoul Kaiser - You could set up an automation rule to auto-transition the appropriate transition based on the field being changed to Yes or No.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Nic Brough -Adaptavist- your approach requires the QA person to know if there is UAT testing and will show 2 buttons they must choose from: UAT and Ready to release. They may not know the correct answer. We can set that field at anytime in the process and setting it will only show 1 field and no one has to guess what comes next in the work flow.
@John Funk I tried to set up the automation but must be doing it incorrectly because it never works. I was using Jira automation but I will see what I can do in the actual work flow.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Erm. " requires the QA person to know if there is UAT testing and will show 2 buttons they must choose from: UAT and Ready to release. They may not know the correct answer"
If they don't know the correct answer, then they can't fill in the field either.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.