Issue Summary
Changing the issue type triggers the issue update event, however this is not the case for converting a task to a sub-task or vice versa. Does not trigger the event when moving to a different level.
The reason being is changing to a sub-task from a Jira expected is not considered an issue update and goes through a different flow. We should look to either introduce new trigger types, or provide an additional option to allow this to trigger on an existing trigger.
Change the issue type triggers the update event, however changing it to Subtasks does not trigger it.
Steps to Reproduce
- Create an automation rule with an update issue event as a trigger.
- Change the issue type to subtasks.
Expected Results
It should trigger the rule.
Actual Results
It is not triggering the rule.
The problem might be related to the lack of a rest API endpoint to convert the issue type to subtasks.
Workaround
No workaround.
Suggestion
Hello,
In my Automation rule, when we convert the issue type using the BULK operation the rule works perfectly.
But whenever we change the issue type from the issue level, then rule doesn't work.
I think Atlassian need to look a bit and requires a few changes in the code and automation rule.
For sure, this is possible. If Atlassian want I can show the steps.
Regards,
Prashant Sultania