We are using the jira integration to be able to create jira issues linked to defects.

In a certain case, we discovered a 'ping-pong' behavior, where a jira status change triggers a qase status change, which in its turn changes the jira status again.

E.g. we set our jira issue from "IN QA/Testing" to "Deployed to stg". This in turn sets the linked Qase defect to "Resolved" (Which is okay. It is not ideal for us, as "deployed to stg is not the final state", but I know we cannot change the status mappings as for now).

However, this change in the qase defect in its turn sets the issue in jira back to "QA completed". In my opinion this second change shouldn't happen. The status change in Qase was triggered by jira, so it shouldn't trigger anything back in jira (which is kind of a ping-pong effect)

As a side-effect, we miss those issues in jira when we filter on status "deployed to stg", causing us to forget testing those.