Vote #71108: Equalize the way how available shared versions are differentiated in target version drop-downs - redmineorg-copy202205 - Redmine

編集操作

リンクをコピー

Vote #71108

未完了

« 前 | 次 »

Equalize the way how available shared versions are differentiated in target version drop-downs

Admin Redmine さんがほぼ2年前に追加. ほぼ2年前に更新.

ステータス:

New

優先度:

通常

担当者:

カテゴリ:

UI_10

対象バージョン:

Candidate for next minor release_33

開始日:

2022/05/09

期日:

進捗率:

予定工数:

Redmineorg_URL:

https://www.redmine.org/issues/9851

category_id:

version_id:

issue_org_id:

9851

author_id:

1565

assigned_to_id:

comments:

status_id:

tracker_id:

plus1:

affected_version:

closed_on:

affected_version_id:

ステータス-->[New]

引用

説明

I'd suggest to equalize the way how available shared versions are differentiated in target version drop-downs since they differ between issues/new and issues/index. See the following screenshots:

I'm happy with either one as long as long as we're presenting a consistent UI.

journals

Fixing ugly typo.
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Fixed description:
* Placed screenshots in table to seperate them better, and reordered them;
* Changed "constant UI" to "consistent UI".
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Make all version fields be presented similarly to the Target Version field (grouped by project name).

Also, take into account that the project name alone does not say much, if the project is in hierarchy with other, similarly named projects. Parent project names should be prepended to the project name.

You can test this and see that version management is impossible in Redmine once there are multiple hierarchy levels and trees.
--------------------------------------------------------------------------------
I just tested this case with the 3.4.4 version of Redmine and it doesn't seem fixed. Custom fields displayed as a list with the _Version_ format aren't prefixed with the project name when issue is edited so you can't distinguish between two versions having the same name but owned by different projects.
--------------------------------------------------------------------------------
+1
Same situation as describe by Gred Burri :
See #28865
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

related_issues

relates,Closed,9850,Differentiate shared versions in version-format custom field drop-downs by prepending its project name
relates,New,15902,Custom Field - Version - Combo list to be grouped by projects..
relates,New,28865,Group items by project in version type custom fields
duplicates,Closed,14449,Versions custom field format