| Key: |
CHD-1307
|
| Type: |
New Feature
|
| Status: |
Open
|
| Assignee: |
Unassigned
|
| Reporter: |
Richard Bone
|
| Votes: |
0
|
| Watchers: |
0
|
Clone this issue
|
|
If you were logged in you would be able to see more operations.
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
When creating a ticket via the parser api, at present there is no way to gracefully handle failures when creating a ticket. At present, if a timeout occurs for example, I can't easily tell if a ticket was successfully created, or if I need to submit it again. An ideal solution to this probem would be to allow the user to provide their own custom id for the ticket which they could then query for to verify its existence. This could potentially even be implemented using the Message-ID header which already exists in the system, there's just no easy way to query for it. Doing so would also make the queue method of the parser api much more useful as I could simply queue the ticket to be created, and I would already have a means to retrieve it rather than having to use the presumably slower parse method simply so I could retrieve cerberus' ticket id.
|
|
|
There are no comments yet on this issue.
|
| |
|
|
Add support for custom ticket id's for tickets created via the parser API