Requesting Work

Requests for enhancements and new processes should be entered in the JIRA work request system. They should include as much detail as possible.

The process for a typical Project Requests includes performing the following steps within the appropriate JIRA “project”. For a list of JIRA projects, go here:

  1. User enters the specifications into a JIRA request, including as much detail as possible.
  2. The project owners will approve (or reject) the project and will prioritize it among other outstanding, local projects.
  3. The technical manager will assign a developer, according to availability, who will begin development in accordance with the project schedule.

The Q&A Training Devlopment group has created a more detailed explanation of the JIRA User Interface.

If you are a new employee, or have never accessed the JIRA system before, you must submit a eCAT form in order to be granted general access to the JIRA system.

After your eCAT form has been processed, if you need access to specific JIRA Projects related to the areas below or you need further assistance, you may send your request via email to the corresponding support group below.

Return to top.

Setting Priorities

Use the following guidelines to select the proper priority for a work requests. This is a very important step that assists the EAS and User Groups in determining the proper order for work assignments across all functional areas.

  1. Blocker – Production down situation needs immediate attention. These issues will be assigned immediately, however completion time will vary depending on the complexity of the issue.
  2. Critical – High visibility, high impact (i.e., affecting the majority of students), and urgent time line for completion.
  3. Major – High impact or there is some time sensitivity to completion.
  4. Minor – Moderate impact or there is some time sensitivity to completion.
  5. Trivial – Low impact or there is no specific time for completion.

Return to top.

Organizing Work Requests

EAS requires users to submit all requests for work via JIRA. Customers who do not have access to the necessary JIRA project may send an email to the appropriate address in the above “Requesting Work” paragraph.

NOTE: An Emergency Request, which may involve situations in which all or part of the application is inaccessible or malfunctioning, or a critical business process cannot be completed successfully, the reporter may telephone, email, or use instant messenger to the responsible EAS support group. However, this must be followed up with a JIRA request at the earliest possible moment. The EAS Support group can assist with getting the JIRA request entered.

When work requests are emailed to the appropriate EAS support group, the request will be entered for the reporter and the reporter will be given access to JIRA to enter all future requests.

EAS uses the JIRA work request system to classify and manage work requests. This allows us to meet our customers’ needs in a timely and efficient manner. JIRA captures information about the work request, including complete descriptions of the work required, importance of the request, and contact information of those involved in the solution. It also tracks work progress and provides a way to communicate with participants in requirements definition and solution delivery.

JIRA uses the concept of “projects” to categorize various work requests, and to establish management ownership of these requests (“project lead”).

Return to top.

JIRA Project Links

Campus Solutions

EAS Technology (EAST)

The EAS Technology department provides the following production operations and technology services to the UT Dallas campus staff, faculty, applicants, and students. Please click here to access the EAS Technology website for further information on how to submit a JIRA ticket regarding one of these services.

  • PeopleSoft/Galaxy Security (Access) Control
  • OnBase Security (Access) Control
  • PeopleSoft Galaxy/Portal Access Development
  • PeopleSoft Database Administration
  • PeopleSoft Galaxy Messages
  • PeopleSoft Integration Broker
  • PeopleSoft Architecture/Mobile/AD/LDAP/SSO
  • Production Control Batch Scheduling (Control M)
  • Version Control
  • Automated Testing/QA
  • Change Management

Financial Management System (FMS) and Human Capital Management (HCM)


Return to top.