[mgherkar]

2 years, 7 months ago in reply to: Retrigger ticket in Butterfly #3301

Up

4

Down

::

To re-trigger incident in butterfly, below are the options.

1. Single ticket: http://localhost:8080/incident-management/rest/ITSMRest/retriggerIncidents?incidents=<incident id>
ex. http://localhost:8080/incident-management/rest/ITSMRest/retriggerIncidents?incidents=1066

2. For multiple incidents: http://localhost:8080/incident-management/rest/ITSMRest/retriggerIncidents?incidents=<incident id>
ex. http://localhost:8080/incident-management/rest/ITSMRest/retriggerIncidents?incidents=1066,1068

[mgherkar]

2 years, 4 months ago in reply to: Groovy operation stuck in In-Progress state (Butterfly SP15) #3556

Up

2

Down

::

This question can not be answer generically. This might be performance issue or improper design of the usecase. We have document for coding standard to be followed while writing groovy SOs or Operators. Please refer below link.

https://digitate.atlassian.net/wiki/spaces/ID/pages/316833794/Groovy+scripting

[mgherkar]

2 years, 7 months ago in reply to: Retrigger ticket in Butterfly #3320

Up

0

Down

::

That’s correct. I am not getting an option to edit so unable to correct that.

[mgherkar]

2 years, 2 months ago in reply to: Retrigger ticket in Butterfly #3305

Up

0

Down

::

To re-trigger incident(s) in butterfly, below are the options.

1. Single incident: http://localhost:8080/incident-management/rest/ITSMRest/retriggerIncidents?incidents=<incident id>
ex. http://localhost:8080/incident-management/rest/ITSMRest/retriggerIncidents?incidents=1066

2. Multiple incidents: http://localhost:8080/incident-management/rest/ITSMRest/retriggerIncidents?incidents=<incident id,incident id2,…incident id n >
ex. http://localhost:8080/incident-management/rest/ITSMRest/retriggerIncidents?incidents=1066,1068,2000