Defect #9762
closedClosing issues with commit should be cross project
0%
Description
Test Case:
- Open an issue in project1, number
<issue>
- Make a commit with
(Fixes: #<issue>)
in project2 - Go to
project2->repository
to update issue tracking (should be a hook ;-)) - Figure that the issue is for project2 and not project1
- Move issue to project2
- Got to
project2->repository
to update issue tracking (should be a hook ;-)) - Issue is not marked as resolved by the commit
As issue number is unique across redmine database, I think the issue should be marked as resolved.
Maybe with a warning for wrong project assignement of the issue.
Regards.
Related issues
Updated by Terence Mill almost 13 years ago
Why don't you add project2 amd project 1 below parent project and manage issue in parent. The it shall work out of the if version sharing is activated box. YOu could also add project 1 below project 2 or try to enable version sharing across als projects. Just an idea.
Updated by Daniel Dehennin almost 13 years ago
Terence Mill wrote:
Why don't you add project2 amd project 1 below parent project and manage issue in parent.
They both have the same parent, but issues are dispatched between projects to be managed by project teams.
The it shall work out of the if version sharing is activated box. YOu could also add project 1 below project 2 or try to enable version sharing across als projects. Just an idea.
Thanks, I'll look at version sharing if it can solve our issue (which is triggered quite often unfortunately).
Updated by Daniel Dehennin almost 13 years ago
Ok, assigning a shared version (across all projects) is not the solution for the test case I described.
After step 5, 6 and 7, the issue is not marked as closed.
Regards.
Updated by Daniel Dehennin almost 13 years ago
I found a reference not really similar #8291.
Regards.
Updated by Daniel Dehennin almost 13 years ago
The cross-project issue handling could be a good thing with multiple fixes, if one commit fix 2 or more issues.
Regards.
Updated by Mischa The Evil almost 13 years ago
Updated by Daniel Dehennin almost 13 years ago
Updated by Slawomir CALUCH almost 13 years ago
I am also experiencing problems with this issue.
We have a main project for our framework. This framework has multiple sub projects.
We have a main project with multiple sub projects.
These sub projects use a few modules from our framework,
When issues are added in the main projects sometimes they are partially fixed with modifications to the framework and closed with another fix in the project or the other way round. They basically are cross project.
Now we open a second issue in the framework linked to the first issue where the framework team (me) can handle the changes reference commits and add info for future references.
In the future we want to keep the framework accessible only to our core team... but we'd like to be able to close for example 5 or 6 issues at the same time if they have been reported in 4 sub projects for example. Each subproject being managed by a different person/team we won't necessarily want to peek into the framework or across projects (NDAs and other constraints).
The ideal would be to be able to reference issues from other projects in our commits and display this reference even if the link to this commit leads to a denied access. At least we would have a good way to follow all commits that have contributed to one issue even from other teams.
Updated by Daniel Dehennin almost 12 years ago
- Status changed from New to Resolved
It works, at least since redmine 1.4.4.
Pushing a commit in a project fixing bug of another project works, the issue message has the form:
Applied by commit <PROJECT>:commit:<COMMIT ID>
I'm closing this issue.
Thanks.
Updated by Etienne Massip almost 12 years ago
- Status changed from Resolved to Closed
- Resolution set to Invalid