No filter defined still seeing records in queue

Originally asked by SANDEEP ADE on 05 November 2019 (original question)


Hi,

we have the connection between alm and jira.

we defined trigger only in alm side to create new defects

but still new records are flowing into the incoming queue in alm from jira.

i am expecting the new record creating only from alm.

once the record created in Jira ,then enable updates on this record bothe from alm and jira.

but unfortunately the new records are getting triggered from Jira even though i haven’t defined any trigger in jira


Comments:

Francis Martens (Exalate) commented on 05 November 2019

Let me rephrase.

  • You have an active sync between ALM and JIRA
  • There is only one trigger defined - on the ALM side, selecting all the defects to be sent over
  • Still there are Jira issues, which trigger defect creation on the ALM side

Is this correct?

SANDEEP ADE commented on 06 November 2019

yes ,thats correct .

SANDEEP ADE commented on 07 November 2019

Any update on this issue ?

Francis Martens (Exalate) commented on 25 December 2019

This one question went into the twilight zone.

Is this still a problem and if so - can you send an exalate support.zip from both sides to our support chnannel

Answer by Ariel Aguilar on 05 March 2021

This post has been handled via support ticket.

Exalate Team