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.

Linking repository files to an issue (Feature #264)

Added by Egon Schmid at 2011-03-06 10:38 am. Updated at 2011-03-18 01:09 pm.

Status:Open Start date:2011-03-06
Priority:Normal Due date:
Assignee:- % Done:


Target version:-
Remote issue URL: Affected version:


I think it would be a good idea to be able to add/link repository files to issues.
So the developer can see which project files need to be edited to finish the issue.
And you could view the files changes by reading the issue details.


Updated by Ian Freeman at 2011-03-07 01:06 am

I just link the revision to the issue, so that you can click on the revision to see what files were affected. As for files that need to be changed/haven't been changed yet, I usually just mention that in a short comment.

Updated by Niels Lindenthal at 2011-03-07 09:10 pm

I like that idea to be able to link a ticket to any project artifact from the repository. Linking a revision to a ticket is very helpful, but in some cases it is not sufficient. Very often I want to link a ticket to the latest revision and not to a specific revision. For example if I ask somebody in a ticket to review one of my documents.

In these case the only way I know is to include a simple link within the description. This is not very convenient. You also have the problem if the document wihtin the repository is renamed. I think the link need to be persistent also if the file is renamed.

Updated by Eric Davis at 2011-03-07 11:04 pm

How is this different than using the source: link?



Updated by Egon Schmid at 2011-03-08 11:08 pm

I've just been thinking of adding a table with at least 2 fields:

- issue_id
- file (with the complete path to the project root)

Updated by Anton Lukashev at 2011-03-18 01:09 pm

Somehow you can do it by using Code Review Plugin . While looking through the code listed in "Repository" tab you can assign task to anyone you need. Not sure if that plugin gives a possibility to check several source files per task.

Also available in: Atom PDF