Services‎ > ‎Requirements & Issues‎ > ‎

Using the RT Guest Account

This is a short guide on using the Requirements Tracking System tool (RT) used in the IGE project to support the collection and handling of requirements from the stakeholders of IGE. The document supports the implementation of the IGE Requirements Management Process. This guide is targeted at those wishing to view and easily register Globus-related requirements with IGE through the lightweight guest account.  Please see the How to Register Requirements with Us section on the Community Requirements page for other ways which may be more suitable for you.
If you experience any issues or difficulties in working with the IGE RT system, then please email

Logging into the RT System

The IGE RT system can be found at  When entering this in your browser, you should see:

Simply enter guest as the username and as the password and select login.

Submitting a New Requirement

After logging in, you should be presented with the following screen:

This screen shows you a number of views of the current tickets in the various queues and allows you to submit new tickets.  Simply select New ticket from the navigation bar on the left or on the top bar to create a new one.
You'll be presented with a set of fields to input requirements data.  Let's look at each of these.
Top-level Details

The first set of fields to think about are:

  • Queue: all tickets are initially submitted to the General queue, to await categorisation by IGE, so you wont need to (and cannot) change this.
  • Requestors: the email address appears here by default, but assuming you wish to be notified when updates to the requirement are made (such as IGE discussions, questions for you, status changes) then add in your email address following a comma, making sure not to remove the support email e.g. ', your@email.address' (without the quotes).
  • Cc: you can add in the email addresses of anyone else you wish to be notify in the event of any changes to the requirement
  • Subject: a short title of the requirement.

Requirement Details

The fields dealing with where the requirement is from, the community, and other similar aspects.  Please enter as much information as you can:

  • Originating Individual: the contact details for the individual requesting the requirement e.g. your full name.
  • Originating Community: short description of any research communities, including production Grid infrastructures, to which you belong which are in need of the requirement.
  • Perceived Need: how urgently the described requirement is needed by its community (1 = not urgent, 5 = very urgent).
  • Desired Timeframe: the ideal timeframe for when a resolution is required.
  • Use Case(s): short descriptions, or links to descriptions, of use cases that involve or relate to the described requirement e.g. for a technical issue you could provide description of the set up, the context of the requirement, etc.
  • Rationale: a short description of why it is an important requirement to solve i.e. its impact.
  • Dependencies: any dependencies (technical or non-technical) of the requirement that you are aware of.
  • Related Information: links to further online resources that help to describe the requirements in further detail e.g project website pages, Wiki entries, papers.
This information provides the important context of the requirement.

Description of the Requirement

Lastly, you can enter a full description of the requirement (you may wish to enter this information first):

When complete, just select Create ticket.  Congratulations - you've just registered a Globus requirement with IGE!  It should now appear in the My open tickets list, and you should be notified by email that the ticket has been created.  You can check back on the progress of the requirement later by logging back into RT's guest account and selecting this requirement from the list.  You can now refer to the Community Requirements page for What Happens Next.