JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for TB-SUPPORT Archives


TB-SUPPORT Archives

TB-SUPPORT Archives


TB-SUPPORT@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

TB-SUPPORT Home

TB-SUPPORT Home

TB-SUPPORT  January 2006

TB-SUPPORT January 2006

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

UKI ROC helpdesk service changes

From:

"Coles, J (Jeremy)" <[log in to unmask]>

Reply-To:

Testbed Support for GridPP member institutes <[log in to unmask]>

Date:

Thu, 12 Jan 2006 17:29:57 -0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (58 lines)

Dear All

For those of you who came to GridPP15 over the last 2 days, I hope that you found the talks and discussions useful. For those who were unable to make it please look at the programme and linked talks here: http://www.gridpp.ac.uk/gridpp15/programme.html when you have time. The second half of my own talk contains information about the status of 2.7.0 and the Service Challenge (transfer test) work together with links you need to be aware of when getting involved with it.

One of the activities mentioned a few times at the meeting is the imminent upgrade of the Footprints service run at RAL for the UKI helpdesk. Below is a message of particular importance to anyone who deals with tickets issued by the UKI ROC (or indirectly GGUS)? For most of you the only request is to clear tickets by 23rd January. More technical information is given than many of you need but please read the message just so you know!

Please send any questions to this list or directly to David Spence.

I am in the process of setting up the UKI monthly meetings for this year and anticipate the next one in early February when we expect 2.7.0 to be formerly released.

Many thanks,
Jeremy




--------------------

Dear helpdesk agents (those of you who resolve tickets via Footprints),
 
We are planning to migrate to a new interface between the local UK/Ireland ROC helpdesk and the GGUS helpdesk (in Germany).  This should make life much easier for everyone involved in answering queries which originate from GGUS for the UK/Ireland ROC (like the COD tickets).

This email explains what will happen over the next few weeks and how it changes the way the helpdesk will work. Please note that there is action that we would like many of you to take before the changeover.

Summary
*******
 
On the 23rd January we will change the helpdesk "project" (within helpdesk.grid-support.ac.uk) used to process queries for UK/Ireland ROC from "GGUS" to "UKIROC", at the same time a direct interface between the GGUS helpdesk in Germany and the UK/Ireland ROC helpdesk will be deployed.  Once this is in place, any issues/tickets raised in the GGUS helpdesk will be automatically copied across to the UK/Ireland helpdesk and any changes to the tickets made locally will be automatically applied to the copy of the ticket at the GGUS helpdesk (note there will be a short delay).  The support address will also change from [log in to unmask] to [log in to unmask] 
 
Change in usage
***************
 
There will be very little difference when using the new project, except more of the information will  be copied over from the GGUS ticket, therefore we ask that the GGUS ticket is not referenced unless really needed.
 
More details for "expert users":
The main difference between the two projects is with the two extra fields "Responsible Unit" and "syncWithGGUS", these set whether the issue is also on the GGUS helpdesk.  Normally you should not edit these fields; they will be set automatically depending on whether the issue originally came from GGUS or from a user contacting the UKIROC helpdesk.  The one situation where they should be edited is when an issue that a user has submitted to the local UKIROC helpdesk is actually for another responsible unit (ie ROC, etc).  In this case select the appropriate responsible unit from the "Responsible Unit" drop down menu or input via email.   When "Responsible Unit" is set to "ROC_UK/Ireland" then the issue remains local (and is not copied to GGUS) unless "syncWithGGUS" is set to "Yes", this will be case for issues that have come from GGUS.  If you wish to mirror an issue on GGUS, but not assign it to another responsible unit then set "syncWithGGUS" to true.
 
What you need to do
*******************
 
For this change over to proceed smoothly we ask that you endeavour to solve all your remaining tickets in the UKIROC/GGUS helpdesks, we will be sending out messages to people with outstanding tickets to remind them of this request.
 
Monday 23rd January will be an at-risk day for the helpdesk service and there is likely to be no service during the actual change over period, which will be during the morning.  We ask that you do not attempt to log-on to the footprints service on the 23rd until we have notified you by email of the completion of the change over. A reminder will be sent.
 
From the 23rd you should ensure that you use the UKIROC "project" for new issues and the "GGUS" project for ones started before 23rd.   The project you are working on can be selected from the small drop-down menu at the top right of the Footprints screen (if you are logged on).  When replying to emails from Footprints they will be filed in the correct project automatically.  If you do have any outstanding issues on the 23rd then these will remain in the OLD helpdesk and we will keep them synchronised with their GGUS helpdesk copy manually.
 
Issues to be aware of
*********************

There are a few limitations of the importer, due to incompatibilities between the Footprints and GGUS model of helpdesks:
* Parts of the history before a GGUS ticket is assigned to the UK/Ireland ROC may not be copied as the GGUS system only allows access to the most recent diary entries. 
* Attachments are currently not copied; this is because they cannot be inserted into the Footprints system without file system access to its server. 
* When a ticket is set to solved in Footprints the interface between the UKIROC and UK helpdesk must supply a solution.  This will normally be chosen as the last field entered from Footprints.  Therefore it is important that when you set a ticket's status to "solved" that you enter at least some text summarising the solution as this is all a user submitting a query to GGUS will be sent in the email notifying them of the solution.
Thank you for your help in this matter and sorry for any inconvenience caused.  Please don't hesitate to contact me if you have any problems ([log in to unmask]). 

David Spence (UKI ROC)
 

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager