I created a token for the authentication in uvdesk.

and I'm unable to fetch tickets using it. There is an internal server error found when trying to fetch tickets.

May I know what did I miss or is there any log file to trace the problem?

When i upload multiple attachments to uvdesk, it only uploads the last file in the set of files sent, and discards the rest. It does not accept an array of files when creating a ticket or replying to a ticket. It only takes one.

Hi!

I am using Python to create new tickets with this code:

import requests

headers = {"Authorization": "Bearer TOKEN"}

payload = {
    "message": "Ticket Message",
    "actAsType": "customer",
    "name": "Name",
    "subject": "Ticket Subject",
    "from": "[email protected]",
}

r = requests.post("http://my_server/api/v1/ticket", data=payload, headers=headers)

print r.content

Now I want to know how can I create this same ticket but with attachment.

Thanks!

Description
When creating a ticket using the api bundle it gets the default ticket type even when sending a type field with the request.

How to reproduce
Create two Ticket Types in the dashboard

• default
• support

Send a POST request to my-domain/api/v1/ticket with

{
    "name": "John Dow",
    "from": "[email protected]",
    "subject": "Example",
    "message": "Testing example.",
    "type": "support"
}

The newly created ticket has the default ticket type.

Possible Cause
In Webkul\UVDesk\ApiBundle\API\Tickets::createTicket we don't do anything with $data['type']

Description
Fetching all Tickets actAsType: customer responds with wrong list , same as agent, full long list of all tickets.

How to reproduce
API GET tickets ActAsType customer

Possible Solution
line 34 $data['actAsEmail'] not defined in api-bundle/API/Tickets.php line 45 similar

Description

I'm trying to fetch the tickets belonging to a particular user. As suggested by the API documentation (https://github.com/uvdesk/api-bundle/wiki/Ticket-Related-APIs) I tried: To send a GET request to this endpoint: {my_localhost_url}/api/v1/tickets?actAsEmail={[email protected]}.

The API response is the same everytime, regardless of the email parameter. So to clarify, everytime I receive a response containing all the tickets no matter their emails.

If I try this: {my_localhost_url}/api/v1/tickets?actAsEmail={[email protected]}&actAsType=customer The API returns an error.

How to reproduce

To reproduce this issue:

1. Donwload and install uvdesk-community-skeleton.
2. Install the api-bundle.
3. Set up your api, following these steps: https://www.uvdesk.com/en/blog/api-resource/.
4. Open Postman and try to fetch tickets belonging to a particular email using the above mentioned method.

Thanks for your help.

How to reproduce
I created a ticket using the API

I made a post request http://localhost:8000/api/v1/ticket/1/thread to reply the thread, and below is the body { "message":"why should I Help you", "actAsType":"customer", "actAsEmail":"[email protected]", "threadType":"reply" } This is the response and no error message in the terminal { "status": false, "message": "An unexpected error occurred. Please try again later." }

https://www.uvdesk.com/en/blog/api-resource/

I installed the API using the following guide the above guide, however when I attempt to pull for example tickets.json or similar using curl I get back a "404: We were not able to find the page you are looking for." page instead.

Am I missing a step here? The API section of the panel is available, and a token has been created.

Description
When installing I get the message

“Could not find package uvdesk/api-bundle. It was however found via repository search, which indicates a consistency issue with the repository”

When specifying a release ie composer require uvdesk/api-bundle:1.0.4 i get the message

“Yor requirements could not be resolved to an installable set of packages” (for all releases i tried this was the answer)

min-stability is set to dev

updated composer and symfony and no change. running php 7.4

1. Why is this change necessary?

There's a bug, so when you try to follow the API instructions, in order to fetch tickets, you can't fetch tickets based on a particular customer email.

2. What does this change do, exactly?

The code below has some problems, I guess:

 $customer = $entityManager->getRepository('UVDeskCoreFrameworkBundle:User')->findOneByEmail($data['actAsEmail']);
  if ($customer) {
      $json = $repository->getAllCustomerTickets($request->query, $this->container, $customer);
  }

The first line:

 $customer = $entityManager->getRepository('UVDeskCoreFrameworkBundle:User')->findOneByEmail($data['actAsEmail']);

Should be:

$email = $request->query->get('actAsEmail');
$customer = $entityManager->getRepository('UVDeskCoreFrameworkBundle:User')->findOneByEmail($email);

Because the API should be expecting the get query params.

The third line:

$json = $repository->getAllCustomerTickets($request->query, $this->container, $customer);

Should be:

$json = $ticketRepository->getAllCustomerTickets($request->query, $this->container, $customer);

because $repository is not defined. I guess we want to access the $ticketRepository to get the customers.

3. Please link to the relevant issues (if any).

I opened a issue here: https://github.com/uvdesk/api-bundle/issues/16

It should be mentioned that if you try to filter by agent, that is still not working. If you try this endpoint: {my_localhost_url}/api/v1/tickets?actAsEmail={[email protected]}&actAsType=agent The API returns:

{
    "status": false,
    "message": "An unexpected error occurred. Please try again later."
}

So I guess there's a problem with this line:

$user = $entityManager->getRepository('UVDeskCoreFrameworkBundle:User')->findOneByEmail($data['actAsEmail']);

You could change $data['actAsEmail'] by $request->query->get('actAsEmail') and the error disappear. The problem is that after that, if we try to filter by agent email the API returns all the tickets everytime.

Description

I'm trying to assign a ticket to a particular agent. As suggested by the API documentation (https://github.com/uvdesk/api-bundle/wiki/Ticket-Related-APIs) I tried: To send a PUT request to this endpoint: {my_localhost_url}/api/v1/ticket/{ticketId}/agent. I assume that "agent", after the last slash, is the id of the agent you want to assign the ticket, isn't it?

The API response that I got is this:

{
    "status": false,
    "message": "No route found for \"PUT /api/v1/ticket/2/4\""
}

I should say that I've verified and the agent id exists. Same thing for the ticket which id is 2.

How to reproduce

To reproduce this issue:

1. Donwload and install uvdesk-community-skeleton.
2. Install the api-bundle.
3. Set up your api, following these steps: https://www.uvdesk.com/en/blog/api-resource/.
4. Open Postman and try to assign a ticket using the above mentioned method.

Thanks in advance!

Description
When replying from the customer account with the postman API so not going to email to the agent side

How to reproduce

Issue 1:

Step 1: Go to the postman side and reply from the customer account Step 2: Now check the agent's email here nothing receives email notification but also going to the customer email with this email template: New Reply Added on ticket #id

Issue 2:

With the same steps with collaborators add in the ticket and reply from the customer or collaborators side so email notifications receive to the own customer and collaborators account but not receive email notifications to agent account.

Issue 3:

If the customer replies from the postman API side so collaborator is not added as a CC in the ticket thread like this:

Possible Solution
If the reply from the customer or collaborator side with the postman API side so should go to email notification to agent and collaborators side with the right email notification:

If a reply from the customer account from the postman side should be collaborator account added as a CC in ticket thread like this:

Description
When replying with a note and forward option added to the customer account so should not be added as a note and forward in the ticket thread

How to reproduce
Step 1: Reply from the postman side with the note and forward option choose Step 2: Here added actAsType and actAsEmail is customer account Step 3: Go to the admin panel and here note and forward added from the customer account:

Note added from the customer account:

Forward added from the customer account:

Possible Solution

If we use reply add from the postman side with the customer account so should not be added a note and forwarded with the customer account because on uvdesk helpdesk from the customer side is not available the note and forward option.

Description
When the ticket is in the trashed tab should not be the agent updated at this moment

How to reproduce
Step 1: Create a ticket and trash the ticket Step 2: Now go to the postman and update the agent from the postman API side with the trashed ticket id

Using this API:

API URL: {helpdesk_url}/api/v1/ticket/{ticketId}

Method: [PATCH]

Authorization: Basic {API token}

Inputs for agent Update:

property: agent(property is agent)

value: agent Id(agent id)

Note: These inputs give in body -> x-www-form-urlencoded

Step 3: Here the ticket agent is updated successfully

Possible Solution
If we are updating the agent with a trashed ticket id from the postman side should not be updated the agent because on the uvdesk helpdesk trashed ticket agent is not updated:

Description
If the ticket deletes permanently from the postman side so attachments are not deleted from the physical path: [public/assets/threads]

How to reproduce

Step 1: Tickets delete permanently from the postman side

Step 2: Now check in the physical path of the project here are attachments not deleted from this path:

[public/assets/threads]

Possible Solution
If we delete permanently from the postman side so attachments should be deleted from the physical path: [public/assets/threads]

Description
If we use multiple attachments in creates tickets and replies from the postman side should be added multiple attachments

How to reproduce
Step 1: Tickets creates or reply from the postman's side with multiple attachments

Step 2: Now go to the admin dashboard and here shown only one attachment:

Possible Solution

If we use multiple attachments in creates tickets and replies from the postman side should be added multiple attachments

Description
If we are creating a ticket from the postman side, click on ticket view showing an error

How to reproduce
Step 1: Ticket created with this case and send:

message : (your message) actAsType : (agent) actAsEmail: (any customer email) name: (customer name) subject: (Ticket subject) from: (Agent Email)

Step 2: Now go to the admin panel and click on the created ticket with this case after clicking on it shows an error:

Possible Solution
If we create a ticket and click on the ticket should be open