Changes between Version 15 and Version 16 of CmsHelpdesk

24/11/15 15:38:56 (5 years ago)


  • CmsHelpdesk

    v15 v16  
    12 In order to raise a new query you need to be an authorised NCAS user or a UK academic user.[[BR]] 
     12In order to raise a new query you need to be an authorised user.[[BR]] 
    1414Login with your Helpdesk username/password (which you will have received when you registered for PUMA) and then select "New Ticket" from the menu bar above.[[BR]] 
    16 If you don't have an account then please contact ncas-umsupport (at)  
     16If you don't have an account then please [wiki:ContactUs email us] to request one.  
    18 [BeginnersGuideToUmHelpdesk User guide for the UM helpdesk]  
     18== User guide for the UM helpdesk ==  
    20 [AdministratorGuideToTickets Administrator's guide to editing tickets] 
     20=== Before raising a query ===  
     22First search the helpdesk to see if this issue has been raised before. If you have access to the Met Office collaboration Twiki check their guide for [ resolving common UM error messages].  
     24If your query relates to Archer, make sure that your {{{/home}}} and {{{/work}}} spaces are visible to the CMS team. To do so run the following commands:  
     26chmod -R g+rX /home/n02/n02/<your-username> 
     27chmod -R g+rX /work/n02/n02/<your-username> 
     30=== Raising a query === 
     32To create a new ticket (ticket is the equivalent of a query/issue), you need to login to Trac.  Trac has a menu bar at the top; Click on login.  Enter the login name you have been supplied with and your password.   
     34Note: Your trac username is the same as the username you use to log in to puma, but the password is different. You will have been supplied with a password when you were given a puma account. 
     36Once logged in, you should see the menu bar change slightly: A message 'logged in as...' will have appeared as well as a menu bar option to create a New Ticket. 
     38Click on the 'New Ticket' option and a form entitled '''Create New Ticket''' should appear.  You should now fill in the following items: 
     40    * Summary - A brief description summarizing the problem or issue. 
     41    * Description - The body of the ticket. A good description of the problem - should be specific, descriptive and to the point. 
     42    * Type - The nature of the ticket (for example, defect or enhancement request)  
     43    * Component - The project module or subsystem this ticket concerns. 
     44    * Cc - A list of other associated people who want to be kept informed of the progress of the ticket.  
     45    * UM Version - Version that this ticket pertains to. 
     46    * Priority - The importance of this issue, ranging from trivial to blocker. 
     47    * Keywords - These can be any words that might help other users when searching the helpdesk. 
     48    * Platform - The machine where the issue occurs, for example puma or Archer. 
     50[[span(style=color: #FF0000, Do not edit the reporter or owner fields. Having your username as the reporter ensure you will be emailed with any updates to your issue. If you edit the owner then the CMS team will not be alerted to the creating of your ticket and therefore may not respond.)]] 
     52Use the '''Preview''' button to see what the results of your formatting look like.  Once you are happy click '''Submit changes'''. 
     54The ticket will be entered into the system and the relevant members of the helpdesk will be emailed.    
     56=== Changing and commenting tickets === 
     58Once a ticket has been entered into Trac, you can at any time change the information by annotating the ticket. This means changes and comments to the ticket are logged as a part of the ticket itself. 
     60When viewing a ticket, the history of changes will appear below the main ticket area. 
     62We use ticket comments to reply to the issues and to inform of progress. Updates to the tickets are then notified to the reporter, owner and anyone listed in the Cc list. 
     64Note: An important feature is being able to use TracLinks and WikiFormatting in ticket descriptions and comments. Use TracLinks to refer to other issues, changesets or files to make your ticket more specific and easier to understand.  
     66=== Information to include in a ticket ===  
     68Include as much information as is relevant, but especially:  
     70* Be sure to include the id of the UM job (eg xbcde).  
     72* Cut and paste any error messages you have.  
     74* Provide the full path to the {{{.leave}}} or other log file containing the error.  
     76== Administrator's guide to editing tickets ==  
     78Information for CMS staff answering queries: AdministratorGuideToTickets