You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
There are some things I'd like to do as part of my JIRA flow but I can't figure out how to accomplish this (I am a Business Analyst and only a JIRA project admin so can't play with the settings myself). My admin has put it in the too hard basket so I'm trying to, with your help, put together concise instructions to find a solution.
Firstly, I have created a document approval workflow which looks like this:
This is a small team so anybody can edit and anybody can test, but a person cannot do both. How can I build a conditional workflow so that if Current User = Developer then they cannot mark as Done, please?
Looking through the JIRA options I see a 'Value Field' condition but this is not constant so unsure if my use case can be dealt with?
I also see there is a 'Separation of Duties condition' however given the flow can go back and forth, would this rule work?
I'm open to any ideas please, perhaps look at approvers rather than such a custom setup?
Secondly, although document edits follow the above process, there is a shorter and more simple process for document archiving. This is what I imagine it would look like to a user.
I am unsure of the best method to have a conditional workflow off to the side of my current flow.
Thanks in advance for reading my problem and extra thanks if you can attempt to help me.
Have a great day, Brendan
Hello @Brendan Sheppard
For document approval workflow V1.2,
The Jira admin can add a Condition to the transition to Done.
Select "User Is In Any Project Role" or "User Is In Any Group" Condition to allow only users in a given project role/group to execute a transition.
Then only allow QAs to move to Done.
Yes, I would create a separate workflow for Archiving.
Project can have multiple workflow
Thanks for your reply LynnG
As mentioned, we don't have the concept of developer and QA teams, any person can develop or test, but that person cannot do both. Therefore, I don't believe this solution works.
That link gives me a 404 error.
I solved my second query by adding a label to the tickets with the different flow and utilising automation to branch.