Vote #73731: show SCM identifier (repository) in associated revisions - redmineorg-copy202205 - Redmine

編集操作

リンクをコピー

Vote #73731

未完了

show SCM identifier (repository) in associated revisions

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

ステータス:

New

優先度:

通常

担当者:

カテゴリ:

SCM_3

対象バージョン:

Candidate for next minor release_33

開始日:

2022/05/09

期日:

進捗率:

予定工数:

Redmineorg_URL:

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

category_id:

version_id:

issue_org_id:

13715

author_id:

56301

assigned_to_id:

comments:

status_id:

tracker_id:

plus1:

affected_version:

closed_on:

affected_version_id:

ステータス-->[New]

引用

説明

If there are multiple SCM per project (possible since 1.4.0, cfr #779), it would be nice to add the SCM identifier in the associated revisions overview.
For example:

h3. Associated Revisions

scm01 - Revision 999
Added by ...
Bugfix for #...

scm02 - Revision 555
Added by ...
Update of documention for #...

Also in the detail of the revision, mentioning the SCM identifier would be nice.

P.S.: SCM identifier must be known by users if they want to reference the SCM-revision in wiki text

journals

--------------------------------------------------------------------------------
(snip)
--------------------------------------------------------------------------------
I've noticed also another thing, when there are commit-messages in a certain SCM (not default in project) referencing another revision, f.e. r555, the revision in these commit-messages are interpreted by Redmine as hyperlinks, but refering to the default SCM.
Imho, the default SCM in commit-messages of an SCM should be the SCM itself (and not default SCM from Redmine)
--------------------------------------------------------------------------------
+1.

I have one more aspiration on this front. When the commit is associated to revision it says "Revision 555". It would ideal if it can also point out if this revision was on 'trunk' or specific 'branch'.

--------------------------------------------------------------------------------
Dipan Mehta wrote:
> I have one more aspiration on this front. When the commit is associated to revision it says "Revision 555". It would ideal if it can also point out if this revision was on 'trunk' or specific 'branch'.

Related feature for mentioning trunk/branch: #5386
I would keep the 2 features seperated, cause the info for my request is normally available in Redmine (no interpretation of SCM data necessary)
--------------------------------------------------------------------------------
The SCM identifier is already mentioned in the activity overview, so same style should be used in associated revisions / detail of revision
> *Associated revisions*
>
> Revision 999 (scm01)
> Added by ...
> Bugfix for #...
>
> Revision 555 (scm02)
> Added by ...
> Update of documention for #...

--------------------------------------------------------------------------------
This issue can be closed as duplicate of #16354
--------------------------------------------------------------------------------

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

related_issues

relates,New,5386,Branch/Tags in Changeset Description
relates,Closed,5242,Display source project for cross-project associated revisions for issues
duplicates,Closed,16354,Add repository name to revisions on Associated revisions.