When I edit a workflow, I can see a warning message when adding a new trigger that says: "This trigger will be deprecated soon. We recommend using triggers in Automation for Jira as an alternative."
I can't find any information about what that is going to take place. Does anyone know a certain date?
I don't know when it is going to be deprecated, but why not go ahead and start setting up that functionality in Automation for Jira?
Here is another post that might be somewhat related though it doesn't answer your question.
What development/code repository tool are you using?
@John Funk I know how to configure it. Thanks for the documentation link.
The reason why I prefer workflows is that they apply globally across all of our projects. Automations have a real problem with usage limitations.
Let's assume we're a team of 20 developers, where each developer produces per day 3 branch creation events, 3 pull request events, and 3 pull request merge events. This totals to 180 automation executions per day for only syncing Jira issues status with branches status. Imaging how many automations do we need to cover all of our automation rules that are not related to code branches.
In this case here (which I believe is a global one), you're enforcing our small team to go premium, by reducing what the standard plan provides so far, which is totally non-sense! Having global workflows is the key factor we're relying on Jira and classic projects, and enforcing manual configuration per project is a very bad idea.
Hi All! We’re excited to share the launch of an announcement banner that lets Jira site administrators communicate directly to their users across their Jira Cloud instance. ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events