Feature #3805

Issue references between issues in other subproject

Added by André H. about 12 years ago. Updated about 1 year ago.

Status:NewStart date:2009-09-02
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Documentation
Target version:-
Resolution:

Description

I think it should be possible to associate issues over project limits, especially if they are subprojects of the same parentproject.
Just now you're getting an error message that tells you "« Related issue » doesn't belong to the same project".

In huge projects with several subprojects an issue of subproject A can depend on an issue of subproject B. This is a common case.
I think at least it should be allowed to create related issues between subprojects with the same parent. Perhaps this can be at least optional for each parentproject.

issue-3805.patch Magnifier (68.6 KB) Matt Wiseley, 2014-12-14 19:00


Related issues

Duplicated by Redmine - Defect #4464: Related issue doesn't belong to the same project Closed 2009-12-21

History

#1 Updated by André H. about 12 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Shame on me.
This feature already exists in another way. Today I stumbled over the applicable option. So this is fixed for me.

#2 Updated by Mischa The Evil about 12 years ago

  • Category set to Documentation
  • Status changed from Resolved to 7
  • Assignee set to Mischa The Evil
  • % Done changed from 100 to 0

Might need documentation improvement... Check later.

#3 Updated by clay gerrard over 11 years ago

Can you please explain the "applicable" option - I only see:
related to
duplicates
blocks
preceeds
follows

All of them seem to generate the same error:
"Related issue doesn't belong to the same project"

#4 Updated by Mischa The Evil over 11 years ago

clay gerrard wrote:

Can you please explain the "applicable" option - I only see:
related to
duplicates
blocks
preceeds
follows

All of them seem to generate the same error:
"Related issue doesn't belong to the same project"

The "applicable option" is a system-setting instead of a relation-type. See RedmineSettings#Allow-cross-project-issue-relations.

#5 Updated by Muntek Singh over 11 years ago

  • Assignee changed from Mischa The Evil to Muntek Singh

#6 Updated by Alex Last over 11 years ago

I also had the same problem. Thanks to this issue report - I found the proper setting in Admin section.
But! I suggest the error message to be changed from

Related issue doesn't belong to the same project

to

Related issue doesn't belong to the same project. Cross-project links are disabled in the system settings. Please, contact your redmine administrator to change that.

This would save some time to many users hitting this rock.

#7 Updated by Muntek Singh almost 11 years ago

  • Assignee deleted (Muntek Singh)

#8 Updated by Jean-Philippe Lang almost 9 years ago

  • Status changed from 7 to New

Assigned issue with no assignee back to New status.

#9 Updated by Matt Wiseley almost 7 years ago

This is actually two issues:

  1. Relating issues across projects when that feature is disabled
  2. Setting a parent ID to a cross-project issue when that feature is disabled

Attached patch file clarifies error messages for both of these conditions.

#10 Updated by Markus Boremski about 1 year ago

Might be closed. Or not?

Also available in: Atom PDF