Set Release Blocker

To update the Release Blocker field on Jira issues automatically, you can use a command-line automation skill that sends a PUT request to the Jira REST API. It sets the field to Approved, Proposed, Rejected, or clears it, and then reads back the value to verify the update.

Setting a release blocker via the Jira REST API requires the JIRA_API_TOKEN and JIRA_USERNAME environment variables. The automation script uses these credentials to authenticate the PUT request and enforce safe operation when modifying issue fields.

Yes, you can clear the Release Blocker field on a Jira issue by passing an empty value to the automation command. The script validates the input and uses the Jira REST API to remove the existing field value.

You need to set a release blocker for OpenShift component readiness when managing regressions during GA and final RC releases. This ensures that component readiness regressions are consistently tracked and surfaced through the Jira issue tracking system.

If the Jira Release Blocker update fails, the automation handles errors and validates input values to prevent incorrect modifications. It verifies the update by reading back the current field value after the change to ensure the REST API request succeeded.