What are completedCycles and ongoingCycles related to the "Time to resolution" SLA CustomField?

[JayJuan Jones]

Hello, I am trying to figure out what are these variables I'm seeing in python related to. Please point me in the right direction. 

completedCycles and ongoingCycles

[Dirk Ronsmans]

Hi @JayJuan Jones ,

SLA can be configured to be multi-cycle SLA's.

Meaning that they can be stopped and restarted again from zero.  This is often used if you have for example a "Time to Response" SLA and you want to be able to to "reset" the goal each time you move from one state to another.

https://confluence.atlassian.com/servicemanagementserver/example-creating-an-sla-with-multiple-cycles-939926419.html

It's just an assumption but I'm gonna guess they have to do with that.

[JayJuan Jones]

so is there any reason why I am unable to see any of this through the Settings in JIRA but one of my developers can see it when trying to extract data using python?

In the system there is nothing related to either completedCycles and ongoingCycles

[JayJuan Jones]

@Dirk Ronsmans any idea?

[Dirk Ronsmans]

@JayJuan Jones ,

Most likely because the data is not that relevant directly on the issue. However when you wish to do reporting on it (thru the api or something else) the data is kept in the backend for you to retrieve and report on it.