Defect #7649
closed
After copying an issue, revision list does not get updated
0%
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'.
Updated by Ivan Cenov almost 14 years ago
I posted the same issue in ChiliProject: https://www.chiliproject.org/issues/200
Updated by Jean-Baptiste Barth over 13 years ago
It's because changesets are linked to an issue only under certain conditions, one of these being the repository project being the same as the issue project (or in the same hierarchy).
I see at least two simple solutions :- link changesets to issues without checking projects equality
- pros: fast, simple
- cons: prevents us from moving repository behaviour at project level in the future (e.g. PA references issues with one keyword, PB with an other keyword)
- rescan for changesets on issue move
- cons: could be long with big repos
Any though about the best solution ?
Updated by Etienne Massip over 13 years ago
We could link changeset to issue without checking projects equality and only display in the issue page the changeset only if visible from the user pov ?
Updated by Ivan Cenov almost 13 years ago
- Status changed from New to Resolved
The second solution is satisfactory for me. I use it after editing revision messages (in case of misspelling issue numbers par ex.).
If no one else is interested in this issue, please close it.
Updated by Jan Niggemann (redmine.org team member) almost 12 years ago
Closing this, status is resolved since 400 days and more (issue was last updated more than 400 days ago)...
Updated by Jan Niggemann (redmine.org team member) almost 12 years ago
- Status changed from Resolved to Closed