Dependencies UI / Terminology #3332

New Issue

GiteaMirror · 2025-11-02T05:08:53-06:00

GiteaMirror commented

2025-11-02 05:08:53 -06:00

Originally created by @bobemoe on GitHub (May 14, 2019).

Great work over at #2531 seems to be functioning well, I've just got a few ideas for UI/Workflow tweaks. Although I completely understand the concept of the blocks/depends on relation, I find the UI, or terminology, confuses this for me a little. I'm often creating the relation the wrong way around.

Personally I would probably find the terminology parent/child less confusing, but I can see why we may prefer something more descriptive.

From within an issue, I can add a dependency. This sets the issue I'm in as the parent (blocker) and the issue I selected as the child (dependency). The issue then comes under the heading "depends on" on the parent issue, and the parent is shown under "blocks" on the child issue.

If I'm creating a child issue, I have to create the issue, then go to the parent, then add the dependency. When we have a big issue that needs to be split up this is not that convenient.

What also may be adding to the confusion is when you add/remove a dependency between issues a comment is added to both issues stating "user added/removed a dependency" however there is no difference between the message so it is impossible to tell which way the dependency is/was from the message alone.

Am I just missing something here? Or could we choose better terminology?

Suggestions:

Consider consistent terminology. Not sure which to pick though!! :/
Dependent / Depends / Depending / Dependency
Blocks / Blocking / Blocker
Parent / Child
A "create sub issue" button on every issue that creates new issue with the parent already set.
The ability to choose the direction of the dependency when its added, so it can be set from the issue, without having to first browse to the parent. This choice would then give a better indication of the direction through the terminology being side by side.

Originally created by @bobemoe on GitHub (May 14, 2019). Great work over at #2531 seems to be functioning well, I've just got a few ideas for UI/Workflow tweaks. Although I completely understand the concept of the blocks/depends on relation, I find the UI, or terminology, confuses this for me a little. I'm often creating the relation the wrong way around. Personally I would probably find the terminology parent/child less confusing, but I can see why we may prefer something more descriptive. From within an issue, I can add a dependency. This sets the issue I'm in as the parent (blocker) and the issue I selected as the child (dependency). The issue then comes under the heading "depends on" on the parent issue, and the parent is shown under "blocks" on the child issue. If I'm creating a child issue, I have to create the issue, then go to the parent, then add the dependency. When we have a big issue that needs to be split up this is not that convenient. What also may be adding to the confusion is when you add/remove a dependency between issues a comment is added to both issues stating "user added/removed a dependency" however there is no difference between the message so it is impossible to tell which way the dependency is/was from the message alone. Am I just missing something here? Or could we choose better terminology? Suggestions: 1. Consider consistent terminology. Not sure which to pick though!! :/ Dependent / Depends / Depending / Dependency Blocks / Blocking / Blocker Parent / Child 2. A "create sub issue" button on every issue that creates new issue with the parent already set. 3. The ability to choose the direction of the dependency when its added, so it can be set from the issue, without having to first browse to the parent. This choice would then give a better indication of the direction through the terminology being side by side.

GiteaMirror added the type/proposal label 2025-11-02 05:08:53 -06:00

GiteaMirror commented

2025-11-02 05:08:54 -06:00

@funkyfuture commented on GitHub (Jan 13, 2021):

that clear terminology must be found for all localizations. eg. the german translations uses "blockiert" which can be used both in active and passive sentences.

with regards to proposal 2. and the parent / child terms: i don't think they fit well for m:n relations.

maybe a tooltip that elaborates in a sentence on a relationship widget would be helpful too.

@funkyfuture commented on GitHub (Jan 13, 2021): that clear terminology must be found for all localizations. eg. the german translations uses "blockiert" which can be used both in active and passive sentences. with regards to proposal 2. and the parent / child terms: i don't think they fit well for m:n relations. maybe a tooltip that elaborates in a sentence on a relationship widget would be helpful too.

GiteaMirror commented

2025-11-02 05:08:54 -06:00

@wohenbushuang commented on GitHub (Sep 10, 2021):

What also may be adding to the confusion is when you add/remove a dependency between issues a comment is added to both issues stating "user added/removed a dependency" however there is no difference between the message so it is impossible to tell which way the dependency is/was from the message alone.

Same problem to me, which with the same expression and icon, both in English and in Chinese. It made me suspect that this function is not working well for the first time, until I saw the side toolbar.

that clear terminology must be found for all localizations. eg. the german translations uses "blockiert" which can be used both in active and passive sentences.

I guess that just use the similar expressions in the side toolbar would be fine. @lunny

@wohenbushuang commented on GitHub (Sep 10, 2021): > What also may be adding to the confusion is when you add/remove a dependency between issues a comment is added to both issues stating "user added/removed a dependency" however there is no difference between the message so it is impossible to tell which way the dependency is/was from the message alone. Same problem to me, which with the same expression and icon, both in English and in Chinese. It made me suspect that this function is not working well for the first time, until I saw the side toolbar. > that clear terminology must be found for all localizations. eg. the german translations uses "blockiert" which can be used both in active and passive sentences. I guess that just use the similar expressions in the side toolbar would be fine. @lunny ![image](https://user-images.githubusercontent.com/15613184/132800670-d3cf8673-e8d2-46d7-ae94-d464066d00e7.png) ![image](https://user-images.githubusercontent.com/15613184/132800573-a44d025f-add6-4dec-a5a5-d80daba8608e.png)

GiteaMirror referenced this issue

2025-11-02 12:21:28 -06:00

[PR #3332] [MERGED] Fix organization profile on mobile devices #16890

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#3332