Closed or rejected issues in Jira come back to Recommended in IriusRisk

If, after configure the Issue workflow status in the settings, you realize that your closed or rejected issues in Jira are coming back to "Recommended" in IriusRisk later than a synchronization, it could be due to a mismatch or lack of a Resolution state in your Jira.

During the sync process, when the ticket in Jira is synced with the countermeasure in IriusRisk, the state of the countermeasure can be updated. The code is checking for the resolution field on the Jira ticket for updating the state of the countermeasure in IriusRisk. This implies that the data filled in the Issue workflow status for "Close issues when" and "Reject issues when" corresponds to the Resolution status of the Jira ticket, not to the status of the Jira ticket.

For more information about the Resolution field in Jira, check:

Best practices on using the "Resolution" field

Jira issues need a resolution

Post functions

Workflow Post Function

Configure advanced issue workflows