Hi community,
We're excited to share something many of you have been asking for - Goals and Projects can now supports automations. This is just the first iteration, so please continue to share your use cases and feedback to help us prioritise the next set automation features.
For Goals and Projects, we’ve added automation triggers to help you automate workflows when your goals and projects change:
For Goals, we've introduced a Goal status changed trigger which monitors for changes to a goal status (e.g. from On track to Off track).
For Projects, we've introduced a Project field value changed trigger which monitors for changes to Status, Target date, Name and Owner fields.
We've also added in smart values that can be used to reference specific attributes of goals and projects which you can configure as conditions or actions - e.g. {{atlassianProject.name}}.
You can combine these triggers with any existing Automation conditions and actions - including sending messages in your chat apps, sending email, creating Jira issues, running a Rovo Agent to achieve workflows like automatically notifying stakeholders when a goal or project is off track.
These are some of the most highly requested use cases that these new goals and projects triggers can help support:
🔔 Get notified when a goal / project goes off track - Stay on top of OKR health. Trigger a Slack message to goal owners or parent goal editors the moment a goal status changes to "Off track" to help surface what needs your attention.
🔔 Alert stakeholders when a project deadline slips - When a project's target date changes, automatically notify the relevant people so nothing falls through the cracks.
📝 Auto-draft feature release communications on project completion - When a project's status changes to "Completed", trigger a Rovo Agent to kick off the required go to market activities like creating release notes and customer blogposts, turning a manual task into an instant, AI-powered action.
To see how step by step instructions for these use cases, check out the support documentation here.
The Goal status changed trigger enables you to monitor for changes specifically to the status field.
Create an automation rule - Click Create rule
Add the trigger - Under Add a trigger, search for and select Goal status changed.
Select which Goals you want the automation to run for in the Goals field. If you want all goals in your instance, leave blank.
Select which statuses to monitor in the dropdown fields, “From status” and “To status”. If you want to monitor any change to status, you can leave the field blank.
Add an action, e.g. Send message / email. In the message payload, you can utilise smart values to make the message dynamic and provide more context.
{{goal.name}} status has changed from {{goal.oldStatus}} to {{goal.status}}.
Project automations use a Project field value changed trigger. If you have used Jira’s “Field value changed” trigger, this pattern will feel familiar to you. If you haven’t before, the flow might feel a bit more involved - this type of trigger has a steeper learning curve but it’s also what makes it extremely flexible.
Create an automation rule - Click Create rule
Add the trigger - Under Add a trigger, search for and select Project field value changed.
Select the field you want to monitor changes for - Name, Owner, Status, Target date. You can select multiple.
Add a condition (optional) - if you want to specify conditions such as specific statuses to monitor, click on {{smart value}} conditions. In the first value field, specify which field you want to add the condition for and in the “second value”, add the value you want to check against.
Add an action, e.g. trigger a release notes agent.
Not sure where to start, or new to triggers and smart values? You don't have to build rules by hand.
In Studio, you can simply describe what you want in plain language - e.g. "Notify me when the status changes on a project I own" - and Rovo will recognise it as an automation use case, propose a plan, and build the rule for you. The generated rule comes with the trigger, conditions, and action already configured, including smart values placed correctly throughout. You can refine the plan with Rovo before building, then tweak anything you like in the builder.
Support documentation for Projects - captures all available smart values for Projects and provides step-by-step instructions to set up automations for key use cases.
Have you set up an automation for your Goals or Projects? Share your use case in the comments - we'd love to see what you've built.
This is just our first step into automations, let us know which triggers or actions you want to see next - your feedback helps us prioritise.
The Atlassian Goals & Projects team
Nicola Sun
5 comments