Using Automation to Conditionally set Dynamic Parent

[Dietrich]

Our clients log support requests for two separate products. During the creation step they complete a custom field called Product, selecting either option A or B.

We have two monthly epics, one for product A and one for product B. So far we have an automation that creates these new support epics on the first day of every month, and automation that closes those epics on the last day of the month. Both work fine.

For now consultants have to manually set the Parent field to one of the Epics based on the client's selection in the Product field - we'd like to automate this.

Ideally we'd like to create an automation that will listen for new support requests being created (as well as changes to the Product field for existing support requests), and then based on the selection it needs to set the Parent field to the relevant monthly Epic for either product A or B. It needs to dynamically switch over to the new monthly Epic on the first day of the new month.

I've tried a bunch of ways but I'm not really winning.

Would love to hear any ideas or alternative ways of achieving this. 

Thank you

[Bill Sheboy]

Hi @Dietrich 

For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected.  Those will provide context for the community to offer ideas.  Thanks!

Until we see those...

I suspect you will need at least two rules (in addition to what you have already).  The key to making this scenario work is being able to successfully identify this month's epic for each product.

1. Triggered on issue create, use your Product field and JQL to identify the parent epic, and set that field.  I recommend using Lookup Issues to do so, and then the key can be used to set the Parent field.  (And...it can send an email / mention alert if unable to identify the parent for assignment.)
2. Triggered on change to the Parent or Product fields (to detect manual tampering), reset the parent accordingly...if that is what you want to do.

For your existing scheduled trigger rule to create the new epics (for the products), that could iterate over any not-done, child issues and re-assign them to the new parent epic.

Kind regards,
Bill