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.
Custom field of type "Version" does not contain all versions belonging to the project (Bug #1280)
In our project we added a custom field "Affected Version".
It should contain all the versions for the project as listed in the regular field "Target Version".
The root project contains the version definitions which are shared along the project tree.
A sub-project called "Software" has one independent release version "V2.30".
Now this is the only version listed in "Affected Version" while "Target Version" lists all project versions.
Even if versions are shared with all projects they are not listed in this field. It seems that a custom version field only lists those version that are defined in the current project and leaves out all inherited versions.
I tested this with current 3.8.0 (Debian 6.0, Apache2 + Passenger, Ruby 1.8.7, rake 10.0.4) and reproduced the same behaviour:
- created new "custom field" for "issues" with type "version" for "all projects"
- set versions of parent project to be visible for "project tree"
=> tested different types how the version are shared, but no affect
- created issue inside child project -> field "target version" shows all versions of parent project, but new version field is empty (or shows only versions of child project)
So the bug should be confirmed now.
Thank you for looking up the related issue(s), Mischa. That's the simple solution I expected.
We are going to decide on moving to JIRA or staying at ChiliProject. To see that there is work in progress would definitely help the pro ChiliProject section arguing.