Validator: With filtering by issue type

[Cláudia Silva]

Hello,

My question is, regarding the validators associated with a workflow (and this workflow has multiple issue types associated with it), is it possible to create a condition that prevents the transaction of a certain state if that field is empty, but ONLY for issue type X?
In my case, I only want to limit this validator to the Bug issue type, but it won't let me because the workflow is shared with other issue types (even though each issue type has a screen and I only added the field to the Bug issue type screen).
Do you know if there's a ticket associated with this situation? Or a solution that doesn't involve workflow duplication.

Thank you.

[Jack Brickey]

You would need to separate out the issue type to a new workflow. You can simply make a copy of the current workflow and associate the desired issue type to it and add your validator. 

[Cláudia Silva]

Thank you very much for the reply, but for organizational reasons I couldn't separate the issue type from the others. Maybe I'll move forward with automations even if it's not as practical as it would be if it were done using a validator.

[Ryan M]

Have you tried creating multiple transitions from/to the same statuses? One for each issue type, and setting a condition to only show the relevant transition for the relevant issue type?

For example,

Let's consider we have statuses To Do and In Progress, and two issue types. Ticket and Bug.

Make 1 transition between the two statuses and call it "Start Bug" and set the condition to only show for Bugs.
Make another transition between the two and call it "Start Ticket" and set the condition to only show for Tickets.

Then for each transition, you can also set unique validators.

Remember, conditions determine whether the transition is visible at all, and validators still let you see the transition exists, but won't let it pass unless the validation is met. 

[Karan Sachdev]

Hey @Cláudia Silva

You will need to have separate workflows for different work types within the same project. You may refer to this article for details: Configure workflow schemes

Thanks!

[Cláudia Silva]

Thank you very much for the reply, I was already aware that the solution could involve creating a new workflow, but it wasn't what I expected because it's convenient for me to have the same workflow for all issue types.

[Maciej Dudziak _Forgappify_]

Hi Claudia, 

Without 3rd party validator there is no easy way. Do you have any Jira Expression-based validators installed on your Jira?

Cheers

[Cláudia Silva]

Thanks for the reply.
No, I don't. Is there one you can recommend?

[Maciej Dudziak _Forgappify_]

There are several options available on the Atlassian Marketplace—look for Jira Expressions Validator. Some free apps allow you to do this, but you will need to learn the Jira Expression syntax.

I’m from Forgappify, and we developed Ultimate Validator, which lets you build custom validators using only the UI, no knowledge is needed. I’m not sure if installing an app is justified for a single use case, but if it is, here’s how it looks:

At the bottom, you can see our Jira Expression Preview, which helps you understand how the expression is built under the hood, so you can reuse it elsewhere if needed.

I hope it will help!

Cheers

[Cláudia Silva]

Thank you so much for your help and the suggested example. I'll look into the various solutions!