Block transition if no subtask exists

[Martina Steiner]

Dear Community,

I have a problem with my workflows since the new workflow editor was switched on. 

I have a transition that shall only be allowed is a sub-task has been created for this work item (The status of that sub-task has to be DONE -> this condition works fine, but I also need to check IF a subtasks exists at all and block the transition otherwise).

In the editor this rule, which has worked fine so far looks now like this: see image

But this does not work. It does not recognize that a subtask exists and the transition is blocked. Now all our work items are blocked at this stage. I would have to remove this condition to get it working again. but I still want to have this check there...

2 questions:

1: Any idea WHY this rule suddenly does not work anymore in the new editor?

2: How can I make the rule work again?

Thanks for your help!

[Karan Sachdev]

Hey @Martina Steiner

Welcome to Atlassian Community!

I configured my workflow using the same rule and it indeed blocks the transition despite the subtask being present.

I checked but couldn't find any bugs logged for this behaviour. Based on my research, it appears that this is the intended behaviour, because the rule checks if the "sub-tasks" field has has a value greater than 0, and not the actual number of subtasks on the work item.

For now, you'll need to remove this rule to ensure the transition is available, but you may create a support ticket for a confirmation that this is the intended behaviour or further assistance.

This would also mean that it's not possible to achieve this (check if a subtask exists or not) using the existing workflow rules in Jira, and you may have to explore third-party apps that offer extended workflow functionalities (like JWME or scriptrunner).

Thanks!