Project

General

Profile

Actions
Copy link

Defect #7649

closed

After copying an issue, revision list does not get updated

Added by Ivan Cenov over 13 years ago. Updated over 11 years ago.

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:

  1. Create an issue #nnn in project PA.
  2. Associate an Subversion repository to project PB.
  3. 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).
  4. Move the issue to project PB.
  5. 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.
  6. Remove the repository, associated to project PB.
  7. Assign the same repository to project PB.
  8. Fetch revisions.
  9. 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
Copy link

Also available in: Atom PDF