On some objects it is meaningless to define criticality, or at least meaningless when only having fields on that object available for the rule
e.g. Action object may not have a RAG, because the RAG is defined on the parent issue
e.g. Test Plan does not hold a field that could represent criticality, but the parent Control might define how critical the Test Plan execution is
e.g. Waivers might reviewed annually with all reviews of equal importance
At it's simplest, being able to allocate 'Not Defined' or 'Not Applicable' (showing as either white or a light neutral colour), would allow us to show that there was no measure of criticality for these tasks. At the moment we can't choose blank as entry is mandatory, and we don't want to choose Low or Medium because this implies a measure of criticality has been calculated.
The ability to base criticality on parent objects may be a useful way to reduce the use of such artifical criticality.
|Priority||Medium - Important|