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 P Claspill

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.