ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

After moving an issue, revision list does not get updated (Bug #200)

Added by Ivan Cenov at 2011-02-18 08:08 am. Updated at 2011-02-20 05:20 pm.

Status:Open Start date:2011-02-18
Priority:Low Due date:
Assignee:- % Done:

0%
Category:SCM
Target version:-
Remote issue URL: Affected version:

Description

I think I found a bug or some omission (in Redmine 1.1.1):

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'.

History

#1
Updated by Ivan Cenov at 2011-02-18 08:11 am

I posted the same isuue in Redmine: http://www.redmine.org/issues/7649

#2
Updated by Felix Schäfer at 2011-02-18 09:40 am

I think it's because revisions are associated on changeset fetch, and if the issue isn't in the same project, no association is created.

#3
Updated by Ivan Cenov at 2011-02-18 11:32 am

I think so too. If this is considered bad behavior I suppose that the solution could be in the procedure that moves issues. It could take a look at recorded (already fetched) changesets and update ... something (that I don't know what it is, because I am not Ruby / Rails / Redmine programmer).

P.S. I saw that I had written "The last two steps...". This should be read as "The last four steps...".

#4
Updated by Eric Davis at 2011-02-19 01:37 am

  • Subject changed from After copying an issue, revision list does not get updated to After moving an issue, revision list does not get updated

#5
Updated by Felix Schäfer at 2011-02-20 05:20 pm

I think a better approach to the changeset-issue links would be to add them all to the DB no matter what an choose which to show based on preferences.

Also available in: Atom PDF