Skip to content

Latest commit

 

History

History
31 lines (18 loc) · 1.15 KB

devsecops-how-to-modify-due-date.md

File metadata and controls

31 lines (18 loc) · 1.15 KB
copyright lastupdated keywords subcollection
years
2022
2022-08-10
DevSecOps, IBM Cloud, expiration date, expiry date, PCE
devsecops

{{site.data.keyword.attribute-definition-list}}

Postponing the due date of an incident issue

{: #due-date-postpone}

If you want to postpone the due date of an incident issue, you can ask for a review from a security focal. Depending on the review, you can postpone the due date by modifying the Due date field in the {{site.data.keyword.gitrepos}} incident issues meta fields. {: shortdesc}

Setting and updating due date on {{site.data.keyword.gitrepos}}{: caption="Setting and updating due date on {{site.data.keyword.gitrepos}}" caption-side="bottom"}

Be sure to reference the security-focal review in the issue, such as providing a link to it in a comment. {: important}

Postponing the due date of an issue that has a PCE

{: #due-date-change-pce}

If you have an issue that has a Public Cloud Security Exception (PCE), you can change its due date to be the same as the expiration date of the PCE so that evidence collection continues up to the PCE expiration date.