Hi everyone!
I have a problem. Some issues have status like done or closed. Also, this issues has a resolution.
But SLA was not stopped.
In database, I see this criterion in table "customfieldvalue":
...{"timeline":{"events":[{"date":1561552301307,"types":["START"]}]},"ongoingSLAData":
{"goalId":116,"startTime":1561552301307,"paused":false,"thresholdData":{"calculatedAt.....
And issues where SLA was stopped after resolution has this criterion:
...{"timeline":{"events":[{"date":1561616106021,"types":["START"]},{"date":1561616266930,"types":["PAUSE"]}]},"ongoingSLAData":{"goalId":111,"startTime":1561616106021,"paused":true,"thresholdData...
I can watch issues where SLA was not stopped by SQL query:
SELECT ji.[ID]
,ji.[pkey]
,ji.[issuenum]
,ji.[RESOLUTION]
,ji.[issuestatus]
,ji.[CREATED]
,ji.[UPDATED]
,ji.[RESOLUTIONDATE]
,cv.textvalue
FROM [SQL12DB3_JIRA].[jira].[dbo].[jiraissue] as ji
join [SQL12DB3_JIRA].[jira].[dbo].[customfieldvalue] as cv
on cv.issue = ji.id and cv.customfield = 12323 and cv.textvalue like '%,"paused":false,%'
where ji.project = 'MyProject' and ji.issuestatus in (10424,11923)
What could be the problem?
Good afternoon, Gustavo!
I think I made a mistake and registered JIRA with another nickname/username. So I have Yaro-info for Bitbucket and yaroinfo for Atlassian. Can you please make it once? They both are connected by the same email i@yaro.info
Hi,
Are you using Bitbucket Cloud? If that's the case, please refer to the following documents for linking it with JIRA Cloud:
Regards,
Gustavo Refosco
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.