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.

Manually Manage Changesets (Feature #198)

Added by Alex Bevilacqua at 2011-02-17 06:54 pm. Updated at 2011-02-18 07:23 am.

Status:Duplicate Start date:2011-02-17
Priority:Normal Due date:
Assignee:- % Done:

0%
Category:Issue tracking
Target version:-
Remote issue URL:http://www.redmine.org/issues/2009 Affected version:

Description

As has been discussed at length on the Redmine issue tracker (issue 2009), the ability to add related revisions to an issue is missing.

There have been patches released, but never merged into the core of the project. This is a useful feature that gives administrators and developers a bit more control over the content of issues when working with projects that contain a repository.

Related issues

duplicates Feature #185: Manually add associated revisions Open 2011-02-11

History

#1
Updated by Toshi MARUYAMA at 2011-02-17 10:41 pm

There is no test in your patch.
So, I can't commit to Redmine.

#3
Updated by Toshi MARUYAMA at 2011-02-17 10:49 pm

You should not use "changeset.revision".

#4
Updated by Toshi MARUYAMA at 2011-02-18 02:08 am

Toshi MARUYAMA wrote:

You should not use "changeset.revision".

Please see.

#5
Updated by Felix Schäfer at 2011-02-18 07:23 am

Alex, Toshi, I'm really sorry but I had overlooked there was an issue for that already, closing this issue in favor of the other one, please continue any discussion there.

  • Status changed from Open to Duplicate

Also available in: Atom PDF