Defect #7116
closed
Fixing keyword: "closes" doesnt close the issue
Added by Pedro Gutierrez almost 14 years ago.
Updated almost 14 years ago.
Description
Committing a change in our SVN repository with the comment:
"closes #9999"
doesn't close the issue anymore.
We've been using this functionality without any problem until we migrated to 1.0.3
And keywords configurations remains the same (see below)
I haven't found anyone reporting this. But due to the huge ammount of issues since v1.03 was released I can't be sure anymore.
Files
- % Done changed from 0 to 50
- % Done changed from 50 to 0
I'm not able to reproduce this on the current trunk (thus not 1.0.x) and I am not aware of any changes to this feature between 1.0.0 and 1.0.3.
Can you please post some logs?
Everything goes Ok iif the repository and the issue belong to the same project.
The problem arises when a commit in one project tries to close an issue from another project
... but, to be honest, I can't guarantee that this worked before we migrated to v1.0.3
You should be able to reference issues of parent projects and subprojects only through commits. This is introduced in r3357 for issue #4674 shipped with Redmine 0.9.2.
- Status changed from New to Resolved
I understand.
We were trying to close an issue belonging to a project that was neither a parent nor a subproject and this is not part of the expected functionality
- Status changed from Resolved to Closed
Also available in: Atom
PDF