How can automation be set up to trigger based on converting a sub-task to a bug (i.e., issue)?

[Bruce Robinson]

Hi All! Currently, my organization has a process where the QA team will convert some Sub-Tasks to Bugs, based on a certain set of criteria. Because of this, I was asked to create an automation rule that would copy the Description field from the Sub-Task to the Steps to Reproduce field in a Bug, and then clear the Description. The reasoning here is because our testing add-on Xray automatically fills the Description with some content when a Sub-Defect is created through a Test Execution. These two fields (Description and Steps to Reproduce) share the same type.

However, the Sub-task is converted to a Bug using "Convert To Issue". Although this changes the issue type without changing the issue key, using a trigger that monitors changes to the issue type field does not seem to work for some reason. I've tested this numerous times on Jira Cloud...for whatever reason, it doesn't recognize the change from a Sub-Task to a Bug in this instance.

I can only capture this process by using a trigger for when an issue is updated, or on the basis of when other fields are changed (like the field for the Request Source). However, these strokes are too broad, and could in some cases cause for some unintended and/or negative effect(s).

First Question: I've managed to circumvent using automation by creating a new sub-task issue type called a Sub-Defect that includes a visible Steps to Reproduce field. However, I'm wondering if I was just doing something wrong with the automation rule, or if there was some way the conversion process could specifically be captured for one type changing to another...any help or ideas this would be greatly appreciated!

Second Question: Is this possibly a bug or just missing capability from Jira automation? Seems odd that there wouldn't be a way to trigger an automation rule if an issue type was changed from a sub-task to an issue, but that's why I'm also wondering if I am just missing something on my end.

Thanks in advance for any help or information you can provide!

[Bill Sheboy]

Hi @Bruce Robinson 

Have you tried using the generic issue updated trigger, and then using the change log to check for issue type changes, from/to?

FYI I found a defect for the opposite of this use case: converting into a sub-task.  The public backlog item has timed-out (closed) and the Code Barrel one is still open:

• https://jira.atlassian.com/browse/JRACLOUD-74536
• https://codebarrel.atlassian.net/browse/AUT-1960

Best regards,
Bill