View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0009062||mantisbt||feature||public||2008-04-15 07:39||2019-05-22 15:39|
|Target Version||Fixed in Version|
|Summary||0009062: Ability to “Show” and “Require” custom fields per “Status change” instead of basing it upon “Update Issue”|
For our organisation it is required to follow our documented “Problem/Change Form” process.
I think it would be convenient to have have fields which are only required when changing to a specific state.
Due to our maturity level of our organization (CMMI level 2/3) we need a lot of data to make good analysis to adjust our processes. Following example of our states/required fields should give an idea of our problem.
Inititiated (fields filled in on Report Issue)
Every state change is handled by a different person. Making some of the fields required (which is absolutely required to make good analysis) makes these fields show up on the interface for each status change until issue is resolved (Verified). However, Some required fields are not known at some point of time. For example, when changing state to Analyzed one does not know the Implementation cost.
On “Manage Custom Fields” page add a separate table (state-change table).
On the ”Update Issue” page:
This results in when changing to a specific state, it shows the:
|Tags||No tags attached.|