Automation Rules for bug notifications

[Jordan Trinklein]

Hey Automation gurus!

I have a few use cases I'm trying to wire up automation rules for, but so far, my testing has not produced the results I'm looking for. 

Here are the situations that I'm trying to create rules for.

1. If a bug is moved from a different product area into mine, then auto-assign the bug to me (and send an email)

2. If a bug's status is changed from any status to OPEN within my jira project, then auto-assign the bug to me (and send an email)

3. If a new bug is created in my Jira project, then auto-assign the bug to me and send me an email.

The 3rd requirement is easy, that's just the new issue is created trigger to then edit the assignee field.

I'm struggling with the first two. I created a rule that would auto-assign if a bug is created with a specific product area in that field, but what I thought would work for editing the product area on an existing bug hasn't produced anything. 

I'm also not sure how I tell the rule to send an email if the status changes to Open from any other status.

I would really appreciate any help you might be able to give! Thank you so much!

[Mikael Sandberg · Accepted solution]

Both of those two automations are pretty simple ones. The second scenario you can trigger on when the issue is transitioned to Open and then just change the condition to check the issue type is a bug. Then edit the assignee, ether via the edit issue field, or the assignee and you can see in the second one.

The first use case would trigger on value changes for the product area an then you add a condition that checks if the product area is yours, and if so set the assignee and send the email.

I would probably skip the email part since Jira will send you a notification anyways when you get assigned an issue, unless you have turned off that email in your user profile.

[Jordan Trinklein]

@Mikael Sandberg - thank you so much for this response. It worked like a charm.

Can I throw ONE MORE use case at ya? 😃

We are trying to figure out how to create an issue in a specific project when a field is set to Y on a feature across all our other projects and then link that feature to the newly created issue in the specific project.

Is that doable?

[Jordan Trinklein]

@Mikael Sandberg I actually got most of the way there. I wired up this rule and it created the issue in the specified project like it was supposed to, but it didn't perform the AND trigger at the end, which was to automatically link the trigger issue to the newly created issue. Do you see anything wrong with how I have it?