Create Bulk Tickets.

Hemanth_L

Hey can i know is there any option to create Bulk tickets in the REI3 Tickets application?
Can we add excel/csv file and update from the backend(Database) so the the ticket will be created?

lsw-fabian

Hi @Hemanth_L,

currently there is no way to create multiple tickets at once - it is possible to create them fast via API, but this may not solve your case.

Things like CSV import can work - i will add this as a new feature request, but I can't say how long it will take to implement.

You could build your own application (upon Tickets) that does only offer a list for CSV importing and a backend function to process them. This would be a moderate task which could be written in less than a day.

Hemanth_L

Ok Thank You

If i have to insert the tickets from the backend can i know what are the dependencies.

lsw-fabian

Of course (btw. all required attributes are display with an * inside the builder)

Most attribute do have pre-selected values, so you have to focus on the following:

(lsw_tickets.ticket.subject)
(lsw_tickets.ticket.description)
(lsw_tickets.ticket.type)
(lsw_tickets.ticket.team)
(lsw_tickets.ticket.criticality)
(lsw_tickets.ticket.requested_for)
(lsw_tickets.ticket.context)
(lsw_tickets.ticket.created_by) -> per default: current user

Hemanth_L

But i have two more attributes to be specified which are,

Start date and last changed, should these values be specified in Unix format only?

And can i also add a custom column to the application?

lsw-fabian

Hemanth_L Start date and last changes are BIGINT attributes, so yes, please use UNIX time to add them.

Please do not make changes to the ticket application itself, because they will be removed in later updates. What fields do you need? If they are useful for others, maybe we can add them into the standard.

Hemanth_L

lsw-fabian
Ok thank you, I will convert the time to UNIX time and add them,
So I'm figuring out to create tickets from the backend so which are the tables I need to look after or only the tickets table?

lsw-fabian

Hemanth_L if you only need the attributes above, then the ticket relation is all you need 🙂

Hemanth_L

Hey,

{
"0(ticket)": {
"subject": "POSTMAN",
"description": "POSTMAN Tickets",
"api_requested_for": ""
},
"2(api_profile)": {
"id": 123
}
}

This is the body im using but im getting the below response so can you pleas look into it.
{
"error": "ERROR: R3_MSG: The selected context has no assignment to a team (SQLSTATE P0001)"
}

And also can you please help me how can i assign mail id as the requestor

Thank you

lsw-fabian

So you want to use the API instead of an own app?
To use the integrated api you have to create a API profile and add the id to your api request. The api profile does contain things like context and team assignment, which are mandatory when creating a ticket.

api_requested_for should contain the mail address of the requestor.

Hemanth_L And also can you please help me how can i assign mail id as the requestor

Sorry, but i do not understand your second question. What do you want to achieve?

Hemanth_L

Yes I'm using the API method instead of an own app,
Now I'm able to create the ticket after creating the API profile
Thank you

Hemanth_L

Is it possible to provide the created_by value directly in the API request body instead of assigning it through the API profile?
If I include created_by in the new version of the API, will it override the default value assigned by the API profile?
Also, if I want to add a date, should it be converted to UNIX timestamp format?

Thank you