🤖 One Automation Rule That Changed Your Life

[Anwesha Pan]

Hey Community! 👋

We all know that moment — you set up an automation rule, it runs for the first time, and you think… "Why didn't I do this sooner?!"

Maybe it's a simple one that auto-assigns issues when they're created. Maybe it's a complex multi-step beast that syncs Jira with Confluence, pings Slack, and makes your morning coffee ☕ (okay, maybe not that last one… yet). 😉

I'll go first:

Mine is a rule that automatically creates a bug ticket when a test execution fails in the CI/CD pipeline. It pulls in the failed test name, the error log, the build number, and the environment details — all neatly formatted in the bug description. No more copying and pasting or manually filing defects at 5 PM on a Friday. Just clean, consistent, actionable bug reports every single time. 🎉

Now it's your turn!

Drop your favorite automation rule below. Whether it's:

• 🐛 A rule that auto-creates defects from failed test runs

• 🔄 A rule that re-opens a bug when a linked test case fails again after a fix

• 🔁 A workflow transition that saved your team hours

• 📊 A rule that updates test coverage status on the parent story when all test cases pass

• 🧹 A cleanup rule that auto-closes stale bugs that haven't been reproduced in 30 days

• 🪄 Something wildly creative that makes your testing life easier

Bonus points if you share:

1. What problem it solved
2. How you set it up (screenshots welcome!)
3. How much time it saves you per week

No rule is too simple or too complex — sometimes the smallest automations make the biggest difference.

Let's build a collection of the community's greatest automation hits! 🚀

[Bill Sheboy]

Hi @Anwesha Pan 

You have posted this same content in at least three locations. The community managers have reminded members to select one location and post there, and then delete any duplicated content.  That will help to focus the conversations.

Here are the locations:

• https://community.atlassian.com/forums/New-to-Jira-discussions/One-Automation-Rule-That-Changed-Your-Life/td-p/3246705
• https://community.atlassian.com/forums/Atlassian-AI-Rovo-discussions/One-Automation-Rule-That-Changed-Your-Life/td-p/3246711
• https://community.atlassian.com/forums/Rovo-for-Software-Teams-Beta/One-Automation-Rule-That-Changed-Your-Life/td-p/3246713

Kind regards,
Bill

[Anwesha Pan]

Thanks @Bill Sheboy , I absolutely forgot that point. I will keep this post and have deleted the others. Thanks again for reminding 🙂

[vineet p]

How you crete rules?

[Anwesha Pan]

Hi @vineet p 

To create the rules, you can achieve this by either creating flow with Rovo or by using a Rovo agent inside an automation flow.

If you want to keep it simple and don't want to use agent, you can follow the below step-by-step instructions to automate by creating flow with Rovo:

1. Go to your Jira space → More actions (…) → Space settings

2. Select Automation from the side panel

3. Click the input box under "Create flows quickly with Rovo"

4. Describe the flow you want, including a trigger and action. For example:

   • "When a bug is created, set the due date in 7 days and email the ticket owner"

5. Select Preview flow to review what Rovo generated

6. Check the summary, add any missing steps

7. Select Enable flow

You can also find the details in this Atlassian documentation.

Hope this helps! 😊

[Suraj Ravindra Gurav]

Cross-Project Comment & Status Sync automation - that's my favorite.

I built it for me first and then our entire team, partner teams liked it so much that, I updated it for all of them.

Result?

We saved 400+ hours a year for everyone.

But the real benefit is far way beyond merely the number of hours we saved. We boosted visibility, transparency and ultimately the collaboration, with adapting a simple Jira habit - atleast 1 commentary update a week.

Now coming to problem we solved - I'm certain that this exists in every team, every company.

Everyone works at the best of their capacity, Jira issues are assigned to them. Projects, activities progress on track, or blocked. But, leadership is unaware of the things and always have 1 single question - "Where do we stand?". And then you need to run through infinite maze of Jira tickets. It takes a lot of time and results in frustration of not getting required piece of info.

That's the thing I solved.