Restrict Ticket approval based on Component = Infrastructure

[Joao Borges]

Hi there,

How could  I make sure only the assignee "MANAGER"  (name -not a role) is the only one able to approve a ticket for development under Component =Infrastructure ?

We already have a screen approved for development for example, but I would like to make sure only assignee"Manager" is able to approve and no one else is able to move ticket on the board for this component.

thanks

[Jack Brickey]

I also recommend using a different issuetype as well.

Regarding the use of automation. Automation is an "after-the-fact" action whereas the requirement it seems is pre-action, i.e. prevent transition. Now you could use automation to reverse the transition after it happened though a bit kludgy. 

Finally, here is an old post where I proposed a 'possible' solution that might give you some ideas - How-to-allow-or-restrict-transitions-based-on-a-field-value . The idea here is to build different statues w/in your workflow w/ different conditions based upon, in your case, components. Admittedly, this might not be what you want.

[Clark Everson]

You maybe able to do this by an add-on such as automation for Jira, however restricting by component is not something you can do via workflow.

So 2 recommendations: Make a different issue type with it's own approval workflow or do an automation. Theres a few ways to do this in automation for Jira. Mine below is only one of the ways to do

it.