Why re-name automation rules to flows?

Question

I really don't understand, why this change was made - so it's even more difficult for users to know, where they can find which feature? So that users even more often mistake workflows with automation flows which already happened before? Or is it to again have tons of documentation where the wording wasn't updated so you now have two key words to search for, if you need a solution?

I get naming changes to unify naming schemes across products, but here it really seems like it's purely a marketing decision, not catering to user need at all.

On top of it all, it would have been great to actually notify users and admins before such a change was made. Now that the automatic notifications about new features don't work anymore, it would have been at least common courtesy to proactively notify admins a few weeks in advance.

Brock Jolet_wkfaaa · Answer

Not only did they rename rules to flows, but they updated the UI without warning. In order to get to the "Flow Details", we have to open a meatball menu now and choose an option from the dropdown. Arguably one of the most important steps, naming and explaining the rule's flow's purpose is now hidden. I don't understand why Atlassian is so set on using hidden menus within hidden menus especially for stuff that admins access; we're using the settings way more often than any normal user.

I was about to write an article to rant about this change, among other recent UI changes that affect admins, but it looks like Atlassian removed my ability to write articles after my last rant post. I guess they don't want the community to discuss the poor UX that has resulted from their changes.

Koloman Pfeffer · Answer

Thanks, I found it later, but there seems to be a bug in the weekly release blog updates as none of our admins receives the emails anymore. Also the blog updates don't seem to be released on Tuesdays anymore.

But yes, the explanation in my opinion is more than questionable and feels very much like a marketing decision actual users won't like.

Aron Gombas _Midori_ · Answer

While I am huge fan of using the right term everywhere and consistently, I don't support this rename.

Particularly because "flows" and "workflows" are now uncomfortably close in terminology within Jira.