Add "Statuses" filter when creating new "Issue" custom fields
Custom fields on issues can be associated with specific Trackers, so a custom field that is associated with "Bug" will be hidden on issues of other types. However, if that custom field is "required" then it is required for every status of that issue throughout its workflow.
In many workflows, specific pieces of information are added to an issue throughout its workflow and not all at the beginning, so it would be most useful if custom fields could reflect this. For example, in the workflow of a "Bug" when the tester sets the status to "Verified" that tester should note the version number that they tested and the environment that they tested it in. If a user sets the bug to "Rejected" they should provide an explanation for why it is rejected.
Currently, we keep all of this information in "Notes" and it is the responsibility of each user to remember what needs to be added based on the status they're switching from/to. However, if we could keep this in custom fields that are selectively shown at specific points in the workflow this would both better enforce compliance and would store that information in a more structured way that we could leverage better in custom queries and reports.
Updated by Mischa The Evil 4 months ago
- Status changed from New to Needs feedback
Zee Prime wrote:
[...] However, if that custom field is "required" then it is required for every status of that issue throughout its workflow.
While this is true, there might be another way to achieve what you need. Such a configuration is very nicely explained by Holger just in #39058#note-3.