Can we just get an option named "Block Transition" in action while working with automation in Jira?

[Prem]

I need an option of "Block Transition" in Components (new action) while working with automation.

See pictures below for better understanding -

Details - 

I need to block transition based on few set of condition where it should affect issue transition only when defined conditions met.

In current scenario, I can design an automation rule with all the conditions specified. But When conditions are met then I only can transition the issue to specific status. Whereas I want to block the transition and send a mail or notification to the user asking to fulfil the required condition.

I can not fulfil my requirement with "Transition Issue" component available in Jira Automation. Because I have designed the workflow in a way where issues can not transition to their previous status until it is being re-opened by QA or any admin resets the status in case of any mistakes. And due to this my automation rule can not transition the issue  to its previous status. Here I am blocked.

And yes I know we need to display an error message when we block any transition or simply I can open the desired field through help of screens and get the value entered by the user. but that option is available in workflow transition.

I don't have any option on workflow transition because if I will block the transition from there, It will affect entire issue type and in all scenarios.

Where as I want to block transition in few conditions and on certain issue types.

Worked with issue type scheme and screens too but unable to find out any solution.

If I can get an option to specify condition while editing workflow transition, that will also help or else if I can get an component "Block Transition" on new action will also resolve my problem.

Thanks,

Premdeep.

[Jack Brickey · Accepted solution]

Hi @Prem , welcome to the community.

It seems that you are trying to use automation to prevent transitions from occurring under certain conditions or lack there of. Assuming this is accurate, you will not be able to cheat that using automation. The reason for this is an automation happens "after the fact". The way to manage blocking transitions is via the workflow and using Conditions or Validators. Please note that this is available only for company manage projects.

if I am miss reading your intent, please let me know.

[Prem]

Hi @Jack Brickey ,

Thanks for your reply. I am glad to know more. But, Jack, What I want is something different. 

I just want to block the transition on certain user defined condition. I know I only can prevent this by conditions under workflow transition. But there also I don't have any option to define my condition. There are only pre-defined conditions are there.

I want it as an enhancement, I am happy if I will get an option to write my own condition while working with workflow transitions.

I have access to company managed project as an administrator. So I already have tried a lot.

Please let me know, If there is any procedure to write my own condition while defining it under workflow transition.

[Jack Brickey]

Hi @Prem , could you describe the precise set of conditions you wish to use to allow the user to transition? I don't know what you mean by "write my own condition". However, out of the box WYSIWYG in the workflow Conditions. There are a number of workflow addons that greatly extend the native offerings. So if you cannot achieve your goal OOTB then maybe an addon will help.

For example... If user in group123 AND Customfield-xxx = "approved" AND "Time spent" is not empty...

[Prem]

Hi @Jack Brickey 

Please find below my condition.

IF project in (AN, IOS) AND issuetype = Bug AND "App Version Code[Number]" is not EMPTY (Then Allow the transition) else Block.

[Jack Brickey]

Ok so the way you could save this is as follows. Ensure that there is a dedicated workflow for Issuetype Bug in both the AN and IOS projects. Then simply add a Condition on the transition(s) where the restriction is required. The Condition should be "Value field " set up as below.