Creating Jira Automation triggered by Issue Type Change

[Stacy Lalumondier]

I'm a novice when it comes to creating Jira automation. We do not have any Jira add-ons for automation and cannot add any add-ons. 

Situation:

Issue Type 1: A Story issue type that has a custom multi-line text field, say Field A.

Issue Type 2: Tech Debt. This is also a standard issue type (just like a story or bug) that has a different custom multi-line text field, say Field B.

I'm trying to create automation so that when a Story issue type is changed to a Tech Debt issue type, Field A's information copies over to Field B. 

I'm able to create automation that can copy that field data over by using the edit issue fields, but I don't know how to get it to trigger when the issue type is changed from Story to Tech Debt. Is there a way to do this? I found the trigger for when Issue Type is changed, but I'm not sure how to apply conditions of was a Story and is now a Tech Debt.

[Kian Stack Mumo Systems · Accepted solution]

Put in the following conditions

[Stacy Lalumondier]

Perfect!! thank you

[Mikael Sandberg]

You can use the changelog smart value to get the previous issue type. This should do it:

{{changelog.issuetype.fromString}}

[GAY LEE HOLLON]

I have tried the following three automations using the answers provided. With and without the Description condition. None of them are working. What am I doing wrong?

I am trying to update the description field when an issue is converted from a sub-task to a story.

[Omar Rashid]

Thought I'd answer here because my research let me to this post - The issue type conversions between a subtask to a work item or a work item to a subtask dont trigger field value issue type changes and for some odd reason even if the conversion gets logged as a issue type update in issue history (if your trigger was issue updated) you can't key off of that because the changelog for issuetype doesn't get fired at all for a conversion. 

Found a suggestion/bug for this at https://jira.atlassian.com/browse/JSWCLOUD-22432 that Atlassian really needs to fix