user-defined field used to define the "project" (e.g. by using component)
|Reported by:||falkb||Owned by:||falkb|
At present, the whole multi-project approach is based on a new custom ticket field 'project' or the new table 'smp_project'.
For defining sub-projects it might be a good idea to use the ticket field 'component' instead. This seems to have a big impact of the internal logic. Another abstraction layer may be used for that.
Maybe we're going to close this ticket with 'wontfix'.