Implement consistent naming convention among item actions in different views
Hello,
From opening another ticket regarding right-click drop down options not showing consistent actions depending on the view, I noticed something else.
Available actions for items (via the right-click dropdown) are not consistently named across different views. Some have minor differences (i.e. capitalization), some use different terms, and some are completely different. Common practice should be to call things the same way across the entire environment to minimize confusion (especially for new users) and to enforce consistent use of terminology. We have our own internal documentation for Wrike and it might be confusing to refer to an action one way because we are working in one view, but a user might be seeing a different term (that means the same thing) in a different view.
Here are some examples of different action references between different views:
- "Copy link" in Table view vs. "Copy Permalink" in List view
- "Open in new tab" in Table view vs. "Open in separate tab" in List view
- "Create from blueprint" in Table view vs. "Create from Blueprint" in List view (minor, but still!)
- "Change status" in Table view vs. "Mark as" in List view (this one is completely different!)
- etc.
Point is, these all do the same thing, but are named differently wherever you go.
Also, speaking of consistency, one thing I like is the use of icons in Table view's right-click dropdown. It would be nice to show these icons on other views' right-click dropdowns as these are icons that appear elsewhere in the environment that a user can easily associate to.
Thanks!
Hi Anna, thanks for pointing this out! It's quite ennoing, but I didn't take the time to complain :-)
Those are excellent observations, Anna Giacobbe. Our team will appreciate your feedback, so I have passed it along. Thank you for taking the time to share it. 🤝
Thank you as well, Florian Kislich, for supporting this post.
Basudha Sakshyarika Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Basudha Sakshyarika Wrike Team member Become a Wrike expert with Wrike Discover
Thanks as always, Basudha Sakshyarika!
Hi folks! Thanks again for this feedback!
I can see that the examples here are about the difference between Table and List Views. I'd like to note that because List view is going away at some point next year, we consider it legacy view and may not make any changes to it anymore. At the same time, if you notice any other examples, please share them - we would really appreciate that!
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
Thanks Lisa, I didn't realize the inconsitency was only regarding list view. Anyway I still hope this view will remain!
Hey Lisa!
Good to know, I wasn't aware if there were still plans to phase List view out!
Somewhat related; does this mean that in the initial Blueprints view, it will be in Table view and not List view?
Love the idea of including the icons in all locations where you right-click to take action! That would be very helpful.
Hi Meredith Selden thanks for the support :)
Anna Giacobbe Yes; it may not have all Table view functionality, but it will be table-based. Hope this helps!
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover