Rule that creates issue, but if issue exists with same summary then just change issuetype of

[Harold Pinther]

Currently, a meeting ticket is generated when the component is set in the epic. If the component is changed again, another meeting ticket is created with a new ticket type. I want to prevent this new ticket creation and would then simply change the ticket type of the existing meeting ticket along with the change to the component. Therefore, it is worth checking whether the automation can prevent further ticket creation when the component is changed.

I have no glule how to handle this. Unless the doubles the rule is working fine.

Thanks in advance

[Trudy Claspill · Accepted solution]

Hello @Harold Pinther 

What is the Summary that you use when you create the Task (vs. the Story)?

Do you use any other values in the Components field? Do you set the Components field to have multiple values?

I'm trying to work out a solution, but I need the above information to complete it.

[Harold Pinther]

Hi Trudy, thanks for jumpin in.

The summary is Project Meetings - {{issue.key}} - {{issue.summary}}

There are only these 2 Components or none.

Harold

[Trudy Claspill]

Would you anticipate intentionally having more than one child issue that has "Project Meetings" in the Summary. Or is the intention that you want to only ever have one of those for a given Epic?

Do Task and Story issue types use the same workflow and the same fields (required and optional)?

[Trudy Claspill]

Hello @Harold Pinther 

Did you find a solution for your problem, or do you still need assistance?

[Harold Pinther]

Hey Trudy, im really sorry for responding that late. The colleague stopped the request, so no need to put more work on it.

Thank you vermy much.