Workflow rules - How to restrict a transition based on the request type?

[Francesc Juventeny]

Hi,

In a team-managed project, I have a complex workflow shared by several request types.

I need to ensure that some of the transitions cannot be performed depending on the request type.

I can't find a way to do this in the Rules because I can't select the Request Type field to indicate the type I need to control.

Restrict transition Rule...

Validate a Field Rule...

How can I do this? Is it possible?

Thank you.

[Marc - Devoteam · Accepted solution]

Hi @Francesc Juventeny 

This is not possible.

You should create a separate work type and workflow and use the request type with these.

Or you can use automation rules to revert the issue when transitioning to the not allowed status, see this KB. 

https://support.atlassian.com/jira/kb/restrict-transition-options-for-issues-in-on-hold-and-pending-with-requester-status/ 

I think this is not best practice, as this could sent notifications to customers. I opt to my 1st option, to keep it clear. Also for reporting and SLA if used.

Or you could look at 3rd party app on the marketplace.

[Francesc Juventeny]

Thanks @Marc - Devoteam for your response.

I think we can do it with automation since it's an internal transition. Let's see if there's a way to send an email to whoever made it.

In the workflow I'm designing, I also need to update a field after making a transition. This field is in the Context Fields section, but it doesn't appear in the Rule, even though others in the same section do. What could be happening?

[Marc - Devoteam]

HI @Francesc Juventeny 

Custom field are not able to be automated in a post function.

You need to use the automation section in the project settings and create automation rules.

Both actions you want can only be done by creating automation ruels, not in the workflow condition, validation or post-function.

[Francesc Juventeny]

So I don't understand why the "Service ID (SID List)" field appears, which is a custom field. Mistery...  :-)

Thank you @Marc - Devoteam 

[Marc - Devoteam]

Hi @Francesc Juventeny 

Ah yes on Team managed some fields can, but only field created in the Team project.

Custom field on global level can't be included.

Or this is a field from a 3rd party ap, as field type SID List is not a type that you can create as options in Jira

[Francesc Juventeny]

"Service ID (SID List)" is a global custom field that we use in several projects.

The only difference I see between this one and the one that doesn't appear to me is that one is "Select List (single choice)" and the other is "Radio buttons".

Thanks