Does JIRA support ODC defect categorization?

Kwabs Kumi

Does JIRA support ODC defect categorization?  Specifically:

• ODC Activity: Design Review, Unit Test, Function Test, etc.
• ODC Trigger: The environment or the condition that led to the exposure of the defects, typically captured in recreate scenarios
• ODC Impact: The potential impact of the defect on the intended user
• ODC Target: Represents the high level artifact that was fixed. When there is a defect in the code implementation relative to the Design or Requirements, developers fix the code and hence 'Code' will be the appropriate target. In cases where the code implementation is different from the specifications in Design or Requirements, if the code implementation is accepted over the Design or Requirements, implicitly those documents would need to be changed and hence 'Design' or 'Requirements' be chosen as the Target. In commerical software development practices, such rigor is not common.
• ODC Defect Type: The scope of the fix (assignment, checking, algorithm, etc.)
• ODC Qualifier: The fix required addition of some missing code or fixing of the existing incorrect code or the removal of extraneous code
• ODC Source: captures the orgin of the code that had the defect (developed in house, reused from a library, etc.)
• ODC Age: Indicates the age of the code that had the defect in terms of its developmental history (Base code from a pervious release, New code for the current release, etc.),

Nic Brough -Adaptavist-

You probably want to actually explain what ODC means here (Office of Drug Control?)

But at a glance, yes, JIRA can record and report on most of those, and probably all of them with a little bit of thought.