Vote #69461: custom issue relation types - redmineorg-copy202205 - Redmine

編集操作

リンクをコピー

Vote #69461

未完了

« 前 | 次 »

custom issue relation types

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

ステータス:

New

優先度:

通常

担当者:

カテゴリ:

Issues_2

対象バージョン:

開始日:

2011/03/13

期日:

進捗率:

予定工数:

Redmineorg_URL:

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

category_id:

version_id:

issue_org_id:

7849

author_id:

21034

assigned_to_id:

comments:

status_id:

tracker_id:

plus1:

affected_version:

closed_on:

affected_version_id:

ステータス-->[New]

引用

説明

In different projects I am using redmine with a number of custom trackers. To define relations between the tickets I would very much like to use other relations than the ones currently available.

For instance, we have trackers for requirements and features. And we would like to be able to define an "implements" relation: feature implements requirement.

The most sustainable solution would be to be able to define custom relation types much like custom fields. I searched for this on the redmine redmine but didn't find anything.

From looking at source:trunk/app/models/issue_relation.rb it seems fairly straightforward to factor out the relation types and define them like custom fields, including symmetry relationships between the types etc.

As we don't have any redmine development capabilities at the moment I hope more people would be interested to have that feature and somebody interested in implementing it :-) With some guidance and advise from experienced redmine developers my team might also be able to contribute to the development.

journals

+1
Would also like to add custom issue relation types.

--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1. In my case, we use support tickets as QA tasks. It would be really helpfull to define relations such as "Tested in" (with simmetry in "Is tested by"). This feature combined with a custom workflow woudl definitely be a great improvement of my daily workflow.
--------------------------------------------------------------------------------
+1
That's a very good idea
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1. This one would be a great addition to many workflows.
--------------------------------------------------------------------------------
+1 This feature would be useful.
--------------------------------------------------------------------------------
+1 Definitely agree. In our organization we assign review tickets for another developer to review our work. We currently use relations to track the review ticket in relation to the work ticket, but it would be nice to have a relationship type for this.
--------------------------------------------------------------------------------
+1 I just found this as well and it would be great to be able to add symmetrical relation types either by plugins, or especially through the admin UI.
--------------------------------------------------------------------------------

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

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

--------------------------------------------------------------------------------
+1 For this feature: our workflow would be "feature x implement request y". _Anyway_, a new type of custom field which accepts issues (#15340), with single or multiple choices, would also suit this need, maybe with better querying capabilities.
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1

It looks like many of the "relationship types" have specific meanings and probably corresponding code level behaviors. I can guess that this is why this isn't already something we can configure for ourselves, like states.

I would like to suggest that the scope of this RFE be focused only on the "Related To" relationship. Specifically:
# Allow the admin to define any number of +aliases+ for "Related To".
# Present the list of "Related To" aliases in the drop-down as if they were each unique.
# Leave the underlying code behavior as-is.
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
Related to #4799?
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------

related_issues

relates,New,13690,Allow plugins to be able to add relationship types
relates,New,15340,Custom field referencing other tickets
relates,New,16117,Add a new type of related issue: "exclusive"
relates,Closed,18034,related issue improvements
relates,New,25384,Add new issue relation type: Obsoletes and Obsoleted_by
relates,New,26786,Complex issue relation
relates,New,7629,Add "causes" and "caused by" issue relationships
duplicates,Closed,11276,Missing related issues "regressed" and "regressed by" (for experts scenario)
duplicates,Closed,11311,New issue relationship