1
0
-1

Hi Exalate Support,


We are implementing Exalate between 2 JIRA Service Management Cloud instances using scripted view.


We are facing errors with our workflow postfunctions. Note : we use the trigger configuration and not the exalate post functions.


One of our transitions includes 4 post functions :

  • Change status (default post function)
  • Assign ticket to user who triggered the event
  • Add comment (default post function)
  • Index (Default)


Those 3 postfunctions trigger 3 synch events that send details to our second instance. For each event (each post function), ALL the values defined in out outgoing scripts are sent to the other instance. (no matter if it changed or not)

Problem : Since the index happens as one of the last postfunctions, the values pushed in the postfunctions 2-3 (before the index) are not yet indexed and are, therefore, different than the details pushed in postfunction 1.

This lead to a status change (back to the value defined before the transition).


Details of Postfunction (focus on status change) :

  • Change status : From “Triage” to “In Progress”.
  • Assign ticket : changed to “Triage” back. (Triage = the status of the ticket before the index)


Is there a way to :

  • *Eithe*r : groups all postfunctions in only 1 single synch event?
  • Or : prevent the synch to push ALL field values. Synch only the value that were changed in the synch event?
  1. Harold Oconitrillo

    Hi,

    Please refer tot the below documentation.

    https://docs.idalko.com/exalate/x/rAjuAg

    Feel free to contact me back for further questions.

    Kind regards

CommentAdd your comment...