-
Suggestion
-
Resolution: Unresolved
-
7
-
12
-
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.
[JSWCLOUD-22432] Trigger support for subtask conversion in Jira Automation
I would have to agree with others this is blatantly a bug and it's very odd this is considered a "suggestion". The automation rules are clearly not triggering on any field when converting to a sub-task or vice-versa. A ticket's history even shows that the fields are indeed being updated "Parent, Issue Type", yet this is not hitting automation rules. In conjunction with https://jira.atlassian.com/browse/JRACLOUD-74083, it makes it impossible to properly integrate Jira into other systems as sub-tasks do not behave properly.
I agree with William and David - this should be considered a Bug and reclassified and prioritized appropriately.
It shouldn't matter whether an issue is a sub-type or not! We should still be able to set an automation rule to trigger based on the issue type changing and have it work regardless of what kind of issue type the ticket is changing to or from.
At the very least there should be some language in the user interface of automation rules that warns users about the limitation.
It would be super helpful for my teams to be able to trigger automation rules based on the issue type changing from the "Field value changed" trigger. I would also be fine using specific "change to a sub-task" or "change to an issue" triggers as Doug suggested, but the "Field value changed" trigger would be even easier for us.
If "field value changed" trigger could either act on ALL issue types, or if the "field value changed" trigger could be set to include an Epic Link being removed or added, that would work for us.
Yes, and...to what David Catriel notes:
Sub-tasks are indeed part of other issues, AND Atlassian decided decades ago to make a design choice to overload the use of Issue Type to represent that condition. While that design choice is still in effect, it also seems reasonable to treat sub-tasks like other issue types which use that field.
Perhaps a better way to solve this for automation is to explicitly implement triggers to detect all possible issue moves (including issue type), and the same behaviors for a true Move Action. That second one will solve the problem of customers trying to implement a "move" in a rule without understanding the implications of an issue type change.
Completely disagree with this having been reclassified as a suggestion. It's a bug. How the product handles issue type changes (and their alerts) under the hood is irrelevant to the question of why conversions to a sub task don't trigger automation rules.
Jira has an automation condition that checks for a type change, which implies it should work for all issues - including subtasks. It currently does not, so this is a bug in the product. Please reclassify and treat it accordingly.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.
We would like to have a separate triggers for:
#1 - Detecting if a SubTask has been converted to an Issue (using "Convert to Issue")
#2 - Detecting if an Issue has been converted to a SubTask (using "Covert to SubTask")
Relying on the "Issue Updated" trigger is not a good solution. As such a rule would get fired way too many times/day.
A possible workaround would be to enhance the "Field Value Changed" to trigger based upon a change to Parent or Epic Link.
Hi everyone,
Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.
Thank you again for providing valuable feedback to our team!
Jira Cloud team
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