Open APIs

 View Only

  • 1.  TMF 621 - troubleticket - description field

    Posted Mar 31, 2023 12:00
    Edited by Zainul Abidin Mulla Mar 31, 2023 14:47

    Hi, 

    The description field in troubleticket entity is one of mandatory attributes and is a part of CTK tests as well. The description can have a wide range of characters and numerals. It can also contain URL and basically it will be a free text used to describe a ticket. 


    For the test case of /troubleTicket?description={{DESCRIPTIONTT01}}

    this involves searching through a large set of data compared to other attributes of troubleticket like status, priority etc which have predefined values. The description search will become a special search and could have its own complex layers of code. E.g to search through description having special characters, url, ascii codes etc becomes an expensive search operation and will affect the request-response latency SLA. 


    Is it possible to modify/remove this test case and not support description for filtering ?




    ------------------------------
    Zainul Abidin Mulla
    Salesforce
    ------------------------------



  • 2.  RE: TMF 621 - troubleticket - description field

    Posted Apr 03, 2023 01:35

    Hi,

    the description search on trouble ticket is an common use case. Because it is common praxis to check if an issue was already reported or not.

    Also if you implement an text search you search for characters and words this is implemented in most databases under the topic full text search.

    Even if not you can do an simple serarch or regex search over the text field. The same apply for the "name" that is the short description of the incident.

    Gruß Thomas



    ------------------------------
    Thomas Lußnig
    T-Systems International Services GmbH
    ------------------------------



  • 3.  RE: TMF 621 - troubleticket - description field

    Posted Apr 07, 2023 00:09

    Hi,

    Thanks for the reply.

    The common usecase to search a ticket can be done through name. The description is a long text area(e.g. of 36000 characters) and text search on such field can be expensive as such description cannot be indexed. This will definitely break the request-response latency SLA.

    Can we explore the possibility to modify/remove this test case and not support description for filtering ?



    ------------------------------
    Zainul Abidin Mulla
    Salesforce
    ------------------------------

    Original Message


Related Content