プロジェクト

全般

プロフィール

Vote #78837

未完了

Support for additional formats for issue autolinks

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

ステータス:
New
優先度:
通常
担当者:
-
カテゴリ:
Text formatting_26
対象バージョン:
-
開始日:
2022/05/09
期日:
進捗率:

0%

予定工数:
category_id:
26
version_id:
0
issue_org_id:
27093
author_id:
312148
assigned_to_id:
0
comments:
1
status_id:
1
tracker_id:
2
plus1:
0
affected_version:
closed_on:
affected_version_id:
ステータス-->[New]

説明

Currently, only # format is used for issue autolinks - which is cool, but having additional formats for issue autolinks could be quite useful in some integration use cases.

New formats should go in same row with formats described in RedmineTextFormattingMarkdown and RedmineTextFormattingTextile for documents, versions, etc. So it should be something like issue#1234 or issue:1234.

Use case:

GitHub repository mirrored to Redmine SCM. Issue tracking done both in Redmine (for end-users) and GitHub (for developers). Need to properly reference GitHub and Redmine issues in commit messages and utilize Redmine's time tracking by commit messages feature.

Problem:

(remove underscores in commit messages)

The issue numbers in commit messages like "Fix #_102 refs #_13 @30m" will be recognized by both Redmine (issues 102 and 13) and GitHub (issues 102 and 13).

GitHub have additional format for issue autolinks, but still the issue numbers in commit messages like "Fix GH-102 refs #_13 @30m" will be recognized by both Redmine (issue 13) and GitHub (issues 102 and 13).

If Redmine would have additional formats for issue autolinks, then commits like "Fix GH-102 refs issue#13 @30m" will be recognized properly by both Redmine (issue 13) and GitHub (issue 102), so described use case will get a chance to live.


journals

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

Admin Redmine さんが約2年前に更新

  • カテゴリText formatting_26 にセット

他の形式にエクスポート: Atom PDF

いいね!0
いいね!0