Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Columns have data when the jira ticket is open but when the ticket is closed, the data is not there

Yilmaz Akdal
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 20, 2024

 

We extract all Jira issues for a department using the Jira API and load it into our database. There are some columns which have date data but when the ticket is closed we can't see this data in the columns. I extracted the full data into a JSON file and the customField has sometimes both ongoingCycle and closedCycles keys as you can see below.And sometimes there is only one of them. I am not sure which one to use ?or should I use both of them? Or do I need add a logic if the status of the ticket is OPEN use ongoingCycle, and CLOSED ,use the closedCycle? 

Many thanks

jira ongoing closed.PNG

1 answer

0 votes
Anandhi Arumugam _Cprime_
Community Champion
September 20, 2024

Hi @Yilmaz Akdal The columns in the screenshot are SLA information. When importing new tickets into JSM you cannot set specific SLA times. The tickets will adhere to the target Project's setup of SLA Goals. Could you please explain your use case on what you would like to achieve?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events