Feature #16818

Allow multiple relationships between two issues

Added by Brad Smith over 6 years ago. Updated over 1 year ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Issues
Target version:-
Resolution:

Description

This happens in the current version of redmine from git (svn r13129), with mysql 14.14.

Steps to reproduce:
  1. Create an issue
  2. Create a copy of that issue
  3. Attempt to create a relation between the issues (e.g. set the copy to FOLLOW the original)

An error will occur:

ActiveRecord::RecordNotUnique (Mysql2::Error: Duplicate entry '31-40' for key 'index_issue_relations_on_issue_from_id_and_issue_to_id': INSERT INTO `issue_relations` (`delay`, `issue_from_id`, `issue_to_id`, `relation_type`) VALUES (0, 31, 40, 'precedes')):
app/controllers/issue_relations_controller.rb:48:in `create'

This index effectively prevents you from creating two relations between the same pair of issues. Shouldn't this combination of relationships be ok?


Related issues

Related to Redmine - Defect #8628: "Related to" reference may yield circular dependency erro... Closed 2011-06-16

History

#1 Updated by @ go2null almost 6 years ago

What you have observed is the current intended behaviour - only one relationship allowed per between any two issues.

This Defect should be closed, or at least turned into a Feature request to allow multiple relationships between two issues.

#2 Updated by Mischa The Evil almost 6 years ago

@ go2null wrote:

[...] or at least turned into a Feature request to allow multiple relationships between two issues.

Such already exists as #8628 which has some patches too. Initial request is for 'related to' relation but the patches includes a fix for 'copied to/from' relations also.

#3 Updated by Mischa The Evil almost 6 years ago

  • Related to Defect #8628: "Related to" reference may yield circular dependency error message added

#4 Updated by Marius BALTEANU over 1 year ago

  • Tracker changed from Defect to Feature
  • Subject changed from 'copied_to' shouldn't conflict with other relation types to Allow multiple relationships between two issues
  • Category changed from Database to Issues

Also available in: Atom PDF