Page tree
Skip to end of metadata
Go to start of metadata

Trouble Ticket API REST Specification - TMF621

To access this API specification you wil need to be logged in

To login with your TM Forum account please click on the Login button below

Login

Don't have an account? You can register by clicking here:

Register

Notice

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to TM FORUM, except as needed for the purpose of developing any document or deliverable produced by a TM FORUM Collaboration Project Team (in which case the rules applicable to copyrights, as set forth in the TM FORUM IPR Policy must be followed) or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by TM FORUM or its successors or assigns.

This document and the information contained herein is provided on an "AS IS" basis and TM FORUM DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

TM FORUM invites any TM FORUM Member or any other party that believes it has patent claims that would necessarily be infringed by implementations of this TM Forum Standards Final Deliverable, to notify the TM FORUM Team Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the TM FORUM Collaboration Project Team that produced this deliverable.

The TM FORUM invites any party to contact the TM FORUM Team Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this TM FORUM Standards Final Deliverable by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the TM FORUM Collaboration Project Team that produced this TM FORUM Standards Final Deliverable. TM FORUM may include such claims on its website, but disclaims any obligation to do so.

TM FORUM takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this TM FORUM Standards Final Deliverable or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on TM FORUM's procedures with respect to rights in any document or deliverable produced by a TM FORUM Collaboration Project Team can be found on the TM FORUM website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this TM FORUM Standards Final Deliverable, can be obtained from the TM FORUM Team Administrator. TM FORUM makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims.

Direct inquiries to the TM Forum office:

240 Headquarters Plaza,
East Tower – 10th Floor,
Morristown, NJ  07960 USA

Tel No.  +1 973 944 5100 
Fax No.  +1 973 944 511

© TM Forum 2015. All Rights Reserved


 

 

 

  • No labels

3 Comments

  1. Hi,

    I have been following TMForum APIs activites for last 3 years to adopt in our organization.

    I have some questions on how to use this API.

    As a software developer, I am not able to understand and create a request payload.  All the information required to create a request should come from swagger specs. 

    1. I would like to understand if this is a recommended template or meant to be used as-is.
    2. Most of the fields are optional except for 'status' and 'statusChangeReason'.  Do these two fields provide sufficient information for a carrier to act towards a meaningful resolution to ticket in timely fashion?
    3. 'id' is optional.  So what happens if two customers give the same value for id, let's say 1?  In my experience, a resource is created upon a POST request and a resource ID is returned in response.
    4. What is the significance of 'creationDate'.  Don't we know when the request is received at server, what is the request received date and time?
    5. 'targetResoultionDate':  If I am a customer I would like to resolve all my problems yesterday.  Why is this an input field, what happens to SLAs?
    6. 'status':  When I am submitting a ticket, can there be any status other than 'submitted'? 
    7. 'statusChangeReason':  My service is down and having issues.  How do I use this field when submitting a ticket?
    8. 'statusChangeDate':  I don't control the status change.  All I know is a problem happend to my service.  What status change date should be there in filing a ticket?
    9. 'relatedParty':  This is really vague.  Again as a developer how am I supposed to use this field?
    10. 'relatedObject':  details are missing.  Is this some identifier I get from service provider to refer the ticket to?

     

    I will be happy to participate towards specifications review if there is such a group.

    Thanks for your time and support,

    regards

    Manoj

  2. Why managedObject isn`t a part of trouble ticket? Isn`t the api should provide a way to relate a TT with a managed Object?

  3. Hi,

    We are adapting TMF-621 in our organisation for interfacing with trouble ticket system. We have to interface for incident and problem tickets

    Is TMF-621 specific for Incident ticket. How about Problem ticket?

    1. Should we have custom extension to add a type to differentiate between incident and problem ticket
    2. Is there any specific specification for Problem ticket management?