Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does not support custom statuses #5

Closed
clarg18 opened this issue Oct 1, 2022 · 3 comments
Closed

Does not support custom statuses #5

clarg18 opened this issue Oct 1, 2022 · 3 comments

Comments

@clarg18
Copy link
Contributor

clarg18 commented Oct 1, 2022

->getTicketByEmail()

returns

Gets\Freshservice\Exceptions\FreshserviceException with message 'Unsupported status'

if the status is not one of the defaults provided.

@clarg18
Copy link
Contributor Author

clarg18 commented Oct 1, 2022

Looks like these are hard-coded in the Ticket class.

    public const STATUS_OPEN = 2;
    public const STATUS_PENDING = 3;
    public const STATUS_RESOLVED = 4;
    public const STATUS_CLOSED = 5;

@asamofal
Copy link

asamofal commented Feb 8, 2023

Hi! Sorry for so long reply.

Regarding Freshservice API documentation only these statuses are available for the tickets. I didn't find the ability to create a custom status, is it possible?

image

UPD: oh, I found it: Admin > Field ManagerForm > Fields

@asamofal
Copy link

asamofal commented Feb 8, 2023

Supporting non-default values (for statuses or any other ticket fields) requires making an extra API call /api/v2/ticket_form_fields.
I can say that the current implementation doesn't ready for that, it requires too many changes. This package was created to fit the requirements of my project, so there are only the entities/endpoints that my project is needed - this is a very little part of what is available on freshservice API.
Unfortunately, I have no time to create and maintain a package with full API support. But you are free to fork this repo...

@asamofal asamofal closed this as completed Feb 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants