Learn how to ingest data from support, issue, or project tracking tools.
Tickets are one of the resource types available in the platform. It's meant to let you ingest data from tools where two parties communicate and track work to resolve issues or deliver incremental value. Customer support requests, service desk tickets, or software development projects are some examples of what you can map to this resource type.
For more information about this resource type, see Tickets.
Organize your data
Before ingesting tickets, we recommend organizing the platform to house your data.
For more information on the best way to organize your data, check Data structure.
The preferred approach is:
- Create a workspace to house your project.
- Inside the workspace, create a folder where you can ingest your data.
For detailed instructions on how to create workspaces and folders, see Hello world.
Prepare to ingest
Preparing the data is the most important part when you're ingesting non-raw resources.
It starts understanding the structure of your data and mapping it to the structure of one the relevant resource type supported by the platform.
It's about telling your code where to go look for a given piece of information and what parameter it must be translated to when you ingest it.
For example, with tickets, you can map fields like
status to their Onna counterpart.
You can download our sample CSV file and use it to test the following steps.
This example shows you how to ingest user stories exported as CSV from Shortcut and saved on a local machine, but you can retrieve the data whatever way is most convenient for you.
|Original parameter||Onna parameter||Description||Example|
|The Reference Number or ID for the ticket at the origin.|
|A Unique Resource Locator for the ticket at the origin. You can either retrieve it or compose it by assembling the different parts that comprise the URL.|
|The title given to the item in your ticketing system|
|The section where the user story is described in detail.|
|The category that the story is classified as. For example, |
|The status of the ticket. For example, |
|The user who requested the user story (may differ from the one creating it). Usually expressed as a username or email.|
|Users who the story is assigned to. Usually expressed as a usernames or emails.|
|Date when the ticket was created. You must use the ISO 8601 format.|
|Date when the ticket was updated. You must use the ISO 8601 format.|
|List of tags associated to the ticket in the origin.|
When your data set is ready, you can make the call to ingest your data.
POST request to the
/tickets endpoint located under
curl --location --request POST 'https://api.onna.com/v1/resources/tickets' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer d3m0deMOd3m0deMOd3m0deMOd3m0deMOd3m0deMOd3m0deMOd3m0deMOd3m0deMOd3m0deMOd3m0d3m0d3m0d3m0' \
"name": "As a developer I want to use the Onna Platform API so that I can ingest any data",
"description": "As a developer I want to use the Onna Platform API so that I can ingest any data I want",
"status": "In progress",
onna_parent_idis the unique ID of the folder where you're placing your tickets
The full list of parameters for the Tickets resource type is available in the Create Ticket endpoint of our API reference.
A successful response (201) returns:
onna_idis the unique ID of the resource in Onna
onna_urlis the URL at which the resource is available
You can confirm that a ticket is ingested correctly.
GET request to the resource's endpoint.
A successful response (201) returns:
"name": "As a developer I want to use the Onna Platform API so that I can ingest any data",,
Now that you learned how to ingest a Ticket resource, you can make the process repeatable to ingest more.