Page MenuHomePhorge
Create Task
Maniphest T15546

Terminology inconsistency: Hashtags vs Tags vs Projects
Open, Needs TriagePublic
Actions

Description

Steps to reproduce and actual outcome:

  1. Go to http://phorge.localhost/project/
  2. Select Create Project to go to http://phorge.localhost/project/edit/form/default/
  3. Set Name to whatever.
  4. Set Additional Hashtags to whateveradd. ("Hashtags")
  5. Go to http://phorge.localhost/tag/whatever/ and see Hashtags: #whatever, #whateveradd ("Hashtags")
  6. Go to http://phorge.localhost/maniphest/task/edit/form/1/
  7. See a field named Tags ("Tags")
  8. Go to an existing task
  9. Edit the project tags of that existing task
  10. See inline line user edited projects, added foo; removed bar. ("Projects")

Expected outcome:
Consistent terminology.

Other comments:
Ended up looking into this due to https://phabricator.wikimedia.org/T288457 with a downstream user reporting confusion about the term "hashtags", assuming they offers separate subcategorization instead of being name aliases.

Event Timeline

aklapper created this task.Jul 10 2023, 12:40
Herald added subscribers: Cigaryno, Matthew, chris and 2 others. · View Herald TranscriptJul 10 2023, 12:40
aklapper added a comment.EditedJul 10 2023, 12:40

Strawman proposal:

  • Rename "Additional Hashtags" to "Project Name Aliases"
  • Rename "Hashtags" to "Project Name Aliases"
  • Rename "Tags" to "Projects"

Haven't spotted the term "slug" in the UI yet, at least.

avivey subscribed.Jul 10 2023, 14:21

Hashtags are not "aliases" - they are single words with # added at the start, that are references to a topic (project).

I agree that "Projects" and "Tags" is used inconsistently - they almost always refer to the same thing. I prefer "Project Tags" as the best choice, because that's technically accurate and simpler to understand (saying objects "are in" a project can confuse users to think about projects being "in" multiple projects).

assuming [additional hashtags] offers separate subcategorization instead of being name aliases.

I have no idea where such understanding comes from. Is it wide-spread? Maybe it's due to bad translation to some language? Is this a person that never heard of hashtags as used in practically all social media?

aklapper added a comment.Jul 10 2023, 14:35

Found a related old upstream: https://secure.phabricator.com/T10326

In T15546#11801, @avivey wrote:

Hashtags are not "aliases" - they are single words with # added at the start, that are references to a topic (project).

That's likely true, however I don't expect most users to have a mental model which distinguishes between associating a "project name" versus one of a project's "hashtags" to a task.

I agree that "Projects" and "Tags" is used inconsistently - they almost always refer to the same thing. I prefer "Project Tags" as the best choice, because that's technically accurate and simpler to understand (saying objects "are in" a project can confuse users to think about projects being "in" multiple projects).

Same here; I usually use "project tags" in our downstream docs to avoid ambiguity between a representation concept in Phorge and an actual code project represented by that concept in Phorge (cf "email" vs "email address").

I have no idea where such understanding comes from. Is it wide-spread? Maybe it's due to bad translation to some language? Is this a person that never heard of hashtags as used in practically all social media?

It is not wide-spread. I've only been told once in a 1:1 with a new user of our instance using default English.

valerio.bozzolan subscribed.Nov 20 2023, 09:48
Content licensed under Creative Commons Attribution-ShareAlike 4.0 (CC-BY-SA) unless otherwise noted; code licensed under Apache 2.0 or other open source licenses. · CC BY-SA 4.0 · Apache 2.0