No filter defined still seeing records in queue

 
2
1
0

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

  1. Francis Martens (Exalate)

    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?

  2. SANDEEP ADE

    yes ,thats correct .



  3. SANDEEP ADE

    Any update on this issue ?

  4. Francis Martens (Exalate)

    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

CommentAdd your comment...

1 answer

  1.  
    1
    0
    -1

    This post has been handled via support ticket. 


    Exalate Team

      CommentAdd your comment...