We use JIRA (with agile) version v6.4.6 and your plugin in version 5.9.0. (the release information for 5.10.0 seem not regarding my actual problem)
I have some troubles with the workflow post function “TTS - Reset SLA”: We are using a simple workflow for bugs:
The transitions from New and Reopen to In Work are called “Start Progress”. From In work to Resolved is called “Resolve” and from Resolved or closed to Reopen are called “Reopen”. Status “Resolved” means, that the issue is going back to the customer, who should move it to “closed” after approval (or to Reopen if necessary).
And for this wf we have two SLA definitions: a. From New or Reopen to In Work (first response time) b. From In Work to Resolved (“multiple transitions” is checked) – this is the sla time for resolution… with a pause for status Customer Action and New. This means, that the sla time for the resolution starts after the first respond – that what we want.
So far, everything works fine after the first run. Now I added the post function “TTS-Reset SLA” for “All SLAs” to the transition “Reopen”, mentioned, that all SLA-values will be reset to zero and the complete process would start again… But I got a very interesting result – reproducible:
When the issue is in status Resolved and I press “Reopen”, the “Working Duration” of SLA a. (first response time) starts again from 0s okay. The working duration and the Pause Duration of SLA b. are still on the last values !? When I refresh the browser, I get the information from JIRA, that the issue was updated now !? Why is there an update during the first browser refresh after the transition?? Everything seems okay (besides the old values for SLA b.) Now I press “Start Progress”: The Working Duration of a. stops at the last value and the value of the Working Duration of SLA b. is continuing !? After a new browser refresh the Working Duration of SLA a. has the value 0 (zero) !?!? And the Working duration of SLA b. is still continuing (also the Pause Duration of b. is still the same) I thought the reset in the post function (during Reopen) should cause, that ALL SLA-time starts from 0s again, but:
Is there anything wrong with my definitions, or is there a bug in TTS? It seems to me, that the post function stops working after the first hit and does not reset all SLA’s…
Thank’s in advance!