Actions
Defect #7649
closedAfter copying an issue, revision list does not get updated
Status:
Closed
Priority:
Low
Assignee:
-
Category:
SCM
Target version:
-
Start date:
2011-02-18
Due date:
% Done:
0%
Estimated time:
Resolution:
Affected version:
Description
I think I found a bug or some omission.
How to reproduce it:
- Create an issue #nnn in project PA.
- Associate an Subversion repository to project PB.
- Commit an revision in this repository and add 'resolved' string in the message with number #nnn. The revision will not appear in the issue #nnn, because it belongs to another project (PA instead of PB).
- Move the issue to project PB.
- You may expect that the revision has appeared in the issue #nnn, but it hasn't. <<< This is what I call a bug or an omission.
- Remove the repository, associated to project PB.
- Assign the same repository to project PB.
- Fetch revisions.
- Take a look at the issue #nnn. The omitted revision is there.
The last two steps resolve the problem, so I think it is now serious one thus I set the priority of the issue to 'Low'.
Actions