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
resolutionstring
The kind of resolution, e.g. "Fix", "Ignored"
typestringrequired
Issue type (Bug, Task, Subtask, Story, Epic). Subtasks and Epics are treated specially.
statusstringrequired
Issue status
statusCategorystringrequired
Issue status category (one of "To Do", "In Progress", "Done")
summarystringrequired
Issue title
descriptionstringrequired
Issue description
urlstring urirequired
URL to issue
prioritystringrequired
Priority of issue
storyPointEstimatenumberrequired
Story point estimate
parentIssuestring
When the issue is part of an epic, the ID of that epic
labelsstring[]required
Any labels applied to issue
sprintKeysstring[]required
IDs of sprints the issue belongs to
creatorobjectrequired
Details of person who created the issue
reporterobjectrequired
Details of person who reported the issue
assigneeobject
Details of the person assignee to the issue
resolverobject
Details of the person who resolved the issue
eventsobject[]required
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