Automation concepts – Heads-up for your decoder ring / terms glossary updates

[#1]

Estimated time to read: 1 minute

TL;DR: the renaming of stuff has reached automation rules...again.

This is a quick heads-up for more name changes based upon last / this week's release blog changes...this time for automation rules.  Apparently...

• "Rule" will soon be called "Flow"
• "Components" will soon be called "Steps"

There is no information provided by the blog entry if the underlying / exported JSON will change to these new terms.  And, as everything internally is a "component", it is unclear if the underlying / exported JSON will also perhaps rename those all at some point, including:

• trigger
• action
• condition
• branch
• special components to handle branch structures
• nested components to handle trigger-conditions, conditions in branches, etc.
• etc.

I hypothesize the JSON will not change, as "project" was not renamed to "space" and "issue" was not renamed to "work item"; same thing for the event references to those things, such as jira:issue_created.

Please let me know your feedback on this article, and as always...happy rule flow writing!

[Darryl Lee]

The Like is for the article, not the change. Thanks @Bill Sheboy :-}

[Paulo]

Hi @Bill Sheboy , just want to say thanks to your contributions to the Atlassian Community forums. I work mostly on in-person community events, so I dont write us much here as I wish due to lack of time, but I read your contributions a lot.

Regarding your hypothesis, I think it's natural that Atlassian might still keep the old names in backend systems (REST APIs, JSON objects, etc), because of backwards compatibility.
I wouldn't be surprised if the backend names remain for a couple more years, or even if they only update them when they launch a new API version.