In the following, we provide an example of how to push your Planning data to Logilica for storage and built-in analytics. The following depicts all possible fields that can be included in an upload of a ticket or issue, both the mandatory and optional fields.
The cURL POST command is below. Note, that the POST command includes the example API token lgca_UeRxFs_3RYRJEJtdYp7j7Wa6DirG5NjiYslsb and the example workspace myworkspace. The command URL also includes a placeholder for the projectID to associate the uploaded issues with. This projectID is obtained from the pm/projects/create endpoint.
UNIX timestamp of when issue was moved to In Progress
resolvedAtnumber
UNIX timestamp of when issue was moved to Done
resolverobject
Details of the person who resolved the issue
resolutionstring
The kind of resolution, e.g. "Fix", "Ignored"
type*string
Issue type (Bug, Task, Subtask, Story, Epic). Subtasks and Epics are treated specially.
status*string
Issue status
statusCategory*string
Issue status category (one of "To Do", "In Progress", "Done")
summary*string
Issue title
description*string
Issue description
url*string (uri)
URL to issue
labels*array of string
Any labels applied to issue
sprintKeys*array of string
IDs of sprints the issue belongs to
priority*string
Priority of issue
storyPointEstimate*number
Story point estimate
parentIssuestring
When the issue is part of an epic, the ID of that epic
events*array of object
List of events that have happened to the issue, in chronological order Note: this must include at least a CREATED event. Other events such as Change Sprint are required for metrics such as sprint overrun
Response
Success - if any sprintIDs were referenced in the dataset, warnings will be given.