JIRA in my world, is normally utilized for
bug software fixes. Issues may be found in the field or at customer sites. Hardware product issues may also be entered into JIRA although I have rarely seen strictly hardware issues in JIRA.
The flaws found in software should be discovered in verification/validation test processes, caught and fixed during design. These might go in JIRA as well depending upon the company.
Non-Conformances found in
processes normally are documented within a Corrective Action System (that could be JIRA as well but requires much work to get it to work correctly due to the nature of the inherent fields).
NCRs - reports written for
non-conforming materials caught during incoming inspection processes; these may be contained in a central database and assigned to the procurement personnel for discussion and closure with vendors. NCRs may also be written for subsequent material deviations as a means to document flaws and capture the expenses (whether to return or scrap, etc. ).
ECARs - an ecar may be written against a contract or subcontract manufacturer who has been found to not follow prescribed requirements for goods/materials. i.e. suppose a label maker was contracted with to provide laminated labels of a x size. Drawings and specs were provided. First article may be good, but a subsequent order is found to be unlaminated and twice the original size. An ECAR with a subsequent request for an
8D report is sent to the manufacturer so that they can do root cause, corrective action, etc.
At any rate, that is my general take on corrective actions after 30 years of auditing. NCR - non-conforming report is pretty generic term so can encompass many types of issues, most companies I have dealt with break it out into "types" as above - each a separate database for ease of use.
