Defect #7116: Fixing keyword: "closes" doesnt close the issue - Redmine

Actions

Copy link

Defect #7116

closed

Fixing keyword: "closes" doesnt close the issue

Added by Pedro Gutierrez almost 14 years ago. Updated almost 14 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Target version:

Start date:

2010-12-16

Due date:

% Done:

Estimated time:

Resolution:

Affected version:

1.0.3

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

fixingKeys.jpg (27.7 KB) fixingKeys.jpg

Pedro Gutierrez, 2010-12-16 12:04

Actions

Copy link

Updated by Mikhail Sviridov almost 14 years ago

% Done changed from 0 to 50

htdecfjtwecjtwjdcwec

Actions

Copy link

Updated by Mischa The Evil almost 14 years ago

% 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?

Actions

Copy link

Updated by Pedro Gutierrez almost 14 years ago

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

Actions

Copy link

Updated by Pedro Gutierrez almost 14 years ago

... but, to be honest, I can't guarantee that this worked before we migrated to v1.0.3

Actions

Copy link

Updated by Mischa The Evil almost 14 years ago

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.

Actions

Copy link