Built as the default: a reason of at least 8 characters, or an NCR number NCR-YYYY-NNNN, or both; the NCR is linked to pesco-ncr. Validation against pesco-ncr comes later.
To answer: keep.
Plan reference: Q27 in docs/PLAN.md (open questions). Answer here; the build takes the default until then.
**Built as the default:** a reason of at least 8 characters, or an NCR number NCR-YYYY-NNNN, or both; the NCR is linked to pesco-ncr. Validation against pesco-ncr comes later.
**To answer:** keep.
---
Plan reference: Q27 in [docs/PLAN.md](https://gt.pescoinc.biz/spencerm/PacketStation/src/branch/main/docs/PLAN.md) (open questions). Answer here; the build takes the default until then.
Q.C. can reject whatever needs to be rejected, but, they cannot approve it without a NCR#. A NCR# has to be provided before acceptance of the failed or rejected item. They do also need to write a detailed reason for rejection upon rejection. They should also be able to upload their NCR to the packet for traceability in the databook
Q.C. can reject whatever needs to be rejected, but, they cannot approve it without a NCR#. A NCR# has to be provided before acceptance of the failed or rejected item. They do also need to write a detailed reason for rejection upon rejection. They should also be able to upload their NCR to the packet for traceability in the databook
Noted: Q.C. may reject anything, and every reject needs a detailed reason. A rejected item cannot be accepted until an NCR number is entered. Q.C. can upload the NCR document to the packet, and it goes into the data book. Recorded in docs/PLAN.md as change C2, to build in phase 10. Closing.
Noted: Q.C. may reject anything, and every reject needs a detailed reason. A rejected item cannot be accepted until an NCR number is entered. Q.C. can upload the NCR document to the packet, and it goes into the data book. Recorded in docs/PLAN.md as change C2, to build in phase 10. Closing.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Built as the default: a reason of at least 8 characters, or an NCR number NCR-YYYY-NNNN, or both; the NCR is linked to pesco-ncr. Validation against pesco-ncr comes later.
To answer: keep.
Plan reference: Q27 in docs/PLAN.md (open questions). Answer here; the build takes the default until then.
Q.C. can reject whatever needs to be rejected, but, they cannot approve it without a NCR#. A NCR# has to be provided before acceptance of the failed or rejected item. They do also need to write a detailed reason for rejection upon rejection. They should also be able to upload their NCR to the packet for traceability in the databook
Noted: Q.C. may reject anything, and every reject needs a detailed reason. A rejected item cannot be accepted until an NCR number is entered. Q.C. can upload the NCR document to the packet, and it goes into the data book. Recorded in docs/PLAN.md as change C2, to build in phase 10. Closing.