SLA conflict using JIRA Service Desk and the VertygoSLA at the same time

Description

We implement the service desk in a project to run in parallel with the vertygo SLA, and found a possible bug that causes a malfunction in the SLA Service Desk to use at the same time with the SLA Vertigo, since when the issue is completed, the SLA Service Desk is automatically opened again and if we close the issue, JIRA Service SLA starts again.

The rules in Vertygo SLA is the same of JIRA Service Desk, so, if Vertygo SLA is closed, JSD necessarily must be closed too, but it's not happened.

In attachments, we can see the JSD SLA - Triagem CSSP is concluded but, SLA - CSSP from Vertygo SLA is running.
Image 1 and 2: Vertygo SLA is different from JIRA Service Desk SLA.
Image 3: JIRA Service Desk works fine without Vertygo SLA.

It's necessary to use both add-ons, because our client need to compare the functionalities and rastreability. There is conflict using JIRA Service Desk and Vertygo SLA in the same issue?

Environment

JIRA / Linux/ Any Browser

Status

Assignee

Unassigned

Reporter

FernandoC

Type Of Support

Maintenance

Additional contacts

None

Affects versions

7.0.5.5

Priority

Major
Configure