Add Validation on Status Transition for One Team in a Project
Asked by Martinez, Diego:

Hello,

Is it possible to add validation that would require issues from only one team to transition to the next status and the rest of the teams can bypass it for an issue type used by multiple teams? Was thinking I could use the Jira express validator with maybe the board's filter, it would be only one person who can advance the issue to the next status.

We have multiple teams in one project and would not like to create a separate issue type or project just for this team.

![Screenshot 2024-07-03 142859.png](/t5/image/serverpage/image-id/333386iE959466B05CE7A6B/image-size/large?v=v2&px=999 "Screenshot 2024-07-03 142859.png")


Answers:
author: Trudy Claspill
body: Hello [@Martinez, Diego](/t5/user/viewprofilepage/user-id/5348680)

How do you identify that a particular issue is owned by a particular team? Are you using the Team field?

comments: author: Martinez, Diego
body: Exactly, we have a team field where I can pull the team ID, the field will be assigned at the point in the workflow where they want to add this validation.


author: Trudy Claspill
body: Can you show us a diagram of your current workflow and point out which status you want to force the one team to go through?

I think this could be done but it will help me give you specific advice if you provide that information.


author: Martinez, Diego
body: It would be after the In Dev status before the QA team would test (In test in Dev)![Screenshot 2024-07-09 084905.png](https://community.atlassian.com/t5/image/serverpage/image-id/334315iF021D971FF6592CF/image-size/large?v=v2&px=999 "Screenshot 2024-07-09 084905.png")


author: Trudy Claspill
body: That workflow is a bit to complicated to decipher visually with all the overlapping transition arrows.

What is the flow you want to enforce for one team? (Replace A \& B with actual status names)

Dev \> A? \> B?

And the workflow you want to allow other teams to use?

Dev \> B?

What are all the outgoing transitions from Dev and the destination status for each?


author: Martinez, Diego
body: Add a status after *In Dev* and before *In Test In Dev* called *Design Review* which this status or the transition to this status would be required for only one team and the rest of the teams could bypass to In Test In Dev.

I guess there could be other options like sending an email to the person who would be performing reviewing the issue as it would only be one person or add a warning to the user sending it to the next status if I could make for only those specific team members.

Outgoing from Dev is In Test In Dev and Done but also back to the below:![Screenshot 2024-07-09 124217.png](https://community.atlassian.com/t5/image/serverpage/image-id/334424iC18218B6D6300E6A/image-size/large?v=v2&px=999 "Screenshot 2024-07-09 124217.png")


author: Trudy Claspill
body: For the transition from In Dev to In Test In Dev you would want to add a Value Field Condition to hide the transition from the one Team. I have not experimented with this to see if you would need to enter the Team ID or the Team Name here. But this method would make the direct transition unavailable to the one team.

![Screenshot 2024-07-09 at 10.46.14?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/334427i7F92C52C144F4EA8/image-size/large?v=v2&px=999 "Screenshot 2024-07-09 at 10.46.14?AM.png")

You can then add the additional status with a transition from In Dev to it, and a transition from it to In Test In Dev.

If you don't want other teams to use that new status and transition path, then you could put Value Field Conditions on each transition that the Team field must be set to the one Team. Then the transitions would be visible only to that one Team.


author: Martinez, Diego
body: Thanks!! This worked, I used my team's GUID and only the one team can view it.

Thanks again


Tags: cloud

expression

jira-cloud

jira-software

validator