Feature #3805
open
Issue references between issues in other subproject
Added by André H. over 14 years ago.
Updated over 3 years ago.
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.
Files
- 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.
- 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.
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"
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.
- Assignee changed from Mischa The Evil to Muntek Singh
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.
- Assignee deleted (
Muntek Singh)
- Status changed from 7 to New
Assigned issue with no assignee back to New status.
This is actually two issues:
- Relating issues across projects when that feature is disabled
- 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.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by