March Hare Trouble Ticket Help

  • Bug Reporting Options
  • Minimum information to submit
  • How to read the bug list.

    Bug Reporting Options

    If you want to report a defect in CVSNT and you do not have a support contract with March Hare Software then you have several options. The following options are in the "fastest to slowest" order:

    If you want to report a defect in CVSNT and you do have a support contract with March Hare Software use one of these options:

    Report bugs for other products here:

    To report a defect in the UD6, UD8 or any other Uniface product then you will first need to create a login (chose "Create new logon" from the login page).

  • [return to help index]

  • Minimum information to submit - all products

    Regardless of which product you are submitting a bug report for, we need to know the following:

    Information to submit with report
  • Product Version Number. All products have a four field version number, eg:
  • Client Operating System Version, Service Pack Level
  • Server Operating System Version, Service Pack Level
  • The exact command that you executed, or the command sequence if there are several steps involved
  • The log file
  •  CVSNT use "cvs -t -t -t command ..."
     CVSNT use "cvsdiag"
     UD6 set "USYS$UD6_PARAMS=debug func fetch select mmf sql, etc etc ... in the ASN file
  • The configuration file(s)
  •  CVSNT send the CVSROOT and on unix the /etc/cvsnt/Pserver configuration file
     Uniface send the ASN file(s) and INI file
  • Affected files
  •  CVSNT send the RCS file (eg: hello.c,v), the file(s) from the sandbox, and a ZIP of the CVS directory in the sandbox
     UD6/UD8 send the XML or CSV file

  • [return to help index]

  • How to read the bug list.

    The tickets are what describes one or several issues, problems if you wish. Every ticket may have one or several actions related to it to describe work in progress or adding sidenotes. A ticket contains several values to describe the issue, starting with ID which is of no real use to the user. Issue date is at what date and time the ticket was created, Last Changed Date is the date at which the last action occurred, The Component specifies which product or part of the product the ticket affects. The owner field corresponds to the user the ticket belongs to, not neccesarily the creator.

    The Version field explains which version is affected by this issue. The status field is either open or closed depending on the ticket status. Closed tickets can be made open again by changing the status again. The description field describes the issue in depth.

    When the issue described in a ticket is updated, actions may be added to reflect that change. Actions are simply a string value with a date for when the action was added.

    Tickets are highlighted according to the following rules to give an indication of their significance:

    Colour coding of tickets in list view
    CriticalCritical bugs cause either irreversible damage to the repository, or compromise the security of the host computer
    EnhancementAdds a feature, introduces new functionality or options
    BlockerPreventing completion or work on other bugs

  • [return to help index]