How to start create an issue after a specified issue is moved to done?
Asked by Lex Baldridge:

I am currently having a problem where after 1 issue is transitioned to done using an automation rule the next issue will not create.

The automation rule used to move the issue to done is shown below:

![Capture 4.PNG](/t5/image/serverpage/image-id/331438i6F348C617525198F/image-size/large?v=v2&px=999 "Capture 4.PNG")

I need to have this rule in place or at least one similar to cause a chain effect.

The Rule I am having issues with is the rule following the epic creation and the first issue creation. I have included the audit log and the actual steps of the rule.

![Capture 6.PNG](/t5/image/serverpage/image-id/331441i9161A34F5C04ECD6/image-size/large?v=v2&px=999 "Capture 6.PNG")![Capture5.PNG](/t5/image/serverpage/image-id/331440iF96B8063D2F88381/image-size/large?v=v2&px=999 "Capture5.PNG")

I am having issues with the issue field condition; I have tried both summary and issue type and get the same error each time.


Answers:
author: Tommaso Gionfriddo _Teklada_
body: Hi [@Lex Baldridge](/t5/user/viewprofilepage/user-id/5514050) ,

Unfortunately it's difficult to diagnose the issue without further information. When you say you have tried issue type in the condition, what do you mean by that?

Does the automation work as expected if you remove that condition and test it?

Could you also please confirm the exact value of the issue ECI2024-143's summary?

comments: author: Lex Baldridge
body: As in issue type I change the condition box to issue type instead of summary and change it to the issue type that is moving.

The automation does work without the condition however I need the condition because there is multiple Issues that have the same transition. Such as Me gate 1 moves from Scott, In progress, or Uncle Jesse to done. And ME Gate 2 also follows the same movement from Scott, In progress, or Uncle Jesse to done.

The summary would change per epic being the part number. So the summary for a certain issue would be the issue name and then a custom field for the part number.


author: Tommaso Gionfriddo _Teklada_
body: It's strange that the condition failed when it was based on issue type, assuming it was set correctly.

Could you please provide a screenshot of the configuration of the Summary starts with condition?


author: Lex Baldridge
body: Here is what it looks like with the issue type:

![Capture7.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/331480iDBE62D7A41DF9421/image-size/large?v=v2&px=999 "Capture7.PNG")

And this is what it looks like with the summary:

![Capture8.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/331479i74F02F7B8F23222A/image-size/large?v=v2&px=999 "Capture8.PNG")


author: Lex Baldridge
body: In addition, if I manual click from in progress to done it will trigger and follow the rule. It is just when it is automated to move to done is when the rule fails.


author: Tommaso Gionfriddo _Teklada_
body: Oh, my apologies then, I misunderstood what problem you were facing.

By default, automations will not be triggered by actions from other automations.

Please enable the checkbox labelled "Check to allow other rule actions to trigger this rule." Which can be found when viewing the automation rule details.

This should solve your problem


author: Jim Knepley - ReleaseTEAM
body: Is it possible that you have multiple statuses with the name "Done" ?

For example, in team-managed projects, I'm pretty sure that every status is specific to that project, so if you have 3 team-managed projects, you could have 3 "Done" statuses.

comments: author: Lex Baldridge
body: There is only one status that equals done, in total there is:

* In Progress
* Scotty
* Phil
* Andys review
* Uncle Jesse
* Dr.Thunderbeef
* Done

All of them flow into the same done section


author: Tommaso Gionfriddo _Teklada_
body: [@Jim Knepley - ReleaseTEAM](/t5/user/viewprofilepage/user-id/5333848), I believe the problem is not related to the status as the automation is being triggered upon status change. There would not be any entry in the log if the issue was being transitioned to the wrong status


Tags: cloud

jira-work-management-cloud