-
Bug
-
Resolution: Fixed
-
Medium
-
1.2.0.2
When we retrieve and issue using rest api values for the SLA fields are not correct.
Here is a snippet from the response:
"customfield_10202":"com.atlassian.servicedesk.internal.sla.model.SLAValue@f245367","customfield_10201":"com.atlassian.servicedesk.internal.sla.model.SLAValue@19df96f5",
It would be very useful if you just return the JSON value on the database.
- is incorporated by
-
JSDSERVER-107 Create a public REST API for JIRA Service Desk
- Closed
- was cloned as
-
DESK-2343 Failed to load
[JSDSERVER-346] SLA Fields' values are not return correctly in JIRA rest
nathon.fowlie right now you could use alternative such as REST endpoint /rest/servicedesk/1/sla/field/all/data/sla
Nathon Fowlie
added a comment - This really needs to be put on the "fix asap" pile instead of getting buried in the todo list. It prevents integration with other BI/Analytics tools which is an complete show-stopper for enterprise users.
Nathon Fowlie
added a comment - This really needs to be put on the "fix asap" pile instead of getting buried in the todo list. It prevents integration with other BI/Analytics tools which is an complete show-stopper for enterprise users. 
Matias Rönnberg
added a comment - It was actually changed to be a major issue on the 28th of May, a bit after doing some correspondence with Atlassian representatives on the issue.
So I'm glad to say that the input was listened to 
Matias Rönnberg
added a comment - It was actually changed to be a major issue on the 28th of May, a bit after doing some correspondence with Atlassian representatives on the issue.
So I'm glad to say that the input was listened to 
Tomasz Mechelewski
added a comment - agree with Matias - it should be treated as a major for sure. Matias Rönnberg
added a comment - How can this be a minor issue? Isn't it one of the most important features of an SLA calculator that you can export your SLA values to reporting for the customer?
This issue is a game-breaker for many organizations that could otherwise start using Jira SD for ticketing.
Matias Rönnberg
added a comment - How can this be a minor issue? Isn't it one of the most important features of an SLA calculator that you can export your SLA values to reporting for the customer?
This issue is a game-breaker for many organizations that could otherwise start using Jira SD for ticketing.
A work around could be exporting your data to Excel sheets and then use that directly or its in CSV format for data integration purposes.
Better Excel Plugin correctly exports the SLA fields (and even applies coloring rules to that, albeit this may be insignificant in this use case
) and you can even apply Excel features to manipulate that (as a Transform part of a full ETL process). Learn more about this
Another tool that enchances this is the Excel Automation Plugin which can do this transformation periodically. (We actually transform JIRA issues to another system this way.)