Feature #385
Custom fields for transitions
| Status: | New | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Custom fields | |||
| Target version: | - | |||
| Resolution: |
Description
Hi,
We miss this feature really!
Would be great if we could define custom fields for transitions (state changes)! For example if somebody want to change
the status then we can force him to tell the reason.
Thx,
Balazs
History
#1
Updated by gabriel scolan about 14 years ago
One workaround solution could be to have a field name "transition_reason" that would be asked to be edited as a "good practice" rule when such a transition occurs. The best way would in fact be to force the user to justify its transition, but the tool can not do everything. May be by limiting the roles allowed for such or such transition will limit the number of person you need to train. Forcing might act on the handling of the tool and its user friendly interface.
regards
gabriel
#2
Updated by Toshi MARUYAMA about 11 years ago
- Category set to Custom fields