Issue references between issues in other subproject
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.
#4 Updated by Mischa The Evil over 11 years ago
clay gerrard wrote:
Can you please explain the "applicable" option - I only see:
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.
#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
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.
#9 Updated by Matt Wiseley almost 7 years ago
- File issue-3805.patch added
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.