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.
Associate ChiliProject issues with Redmine issues (Task #62)
| Status: | Closed | Start date: | 2011-01-13 |
|---|---|---|---|
| Priority: | Normal | Due date: | |
| Assignee: | Eric Davis |
% Done: | 0% |
| Category: | ChiliProject - Organization | ||
| Target version: | - | ||
| Remote issue URL: |
Description
We will need some way to say "ChiliProject issue #1 is Redmine.org issue #5000". I'm thinking a custom field with the urls would be easiest, called "Remote issue id". That way we can also link issues to other bug trackers like Debian or Rails.
Thoughts?
History
Updated by Holger Just at 2011-01-13 11:37 pm
How about a slightly adapted version of https://github.com/edavis10/redmine_simple_support? That way, we could actually have real links.
Updated by Wieland Lindenthal at 2011-01-14 12:23 am
+1
I think providing special fields to frequent external sources is a great idea.
Updated by Eric Davis at 2011-01-14 08:27 am
I use redmine_simple_support and wouldn't recommend it for us:
- there is a bug preventing it from being set on new issues. Caused by Redmine and it's
Issue#safe_attributes(which will be fixed eventually) - changes to that field are not logged into journals
If we start with a custom field, we can migrate to this plugin later. I'm going to write a migration script for myself anyways (Custom Field -> Simple Support urls).
Updated by Eric Davis at 2011-01-21 05:47 pm
I added a Remote Issue Url field that we can use. Later on when we add a URL custom field type we can have it automatically link. (I have a prototype version that is almost ready)
- Assignee set to Eric Davis
- Status set to Closed