About IU Enterprise JIRA

On this page:


Overview

JIRA is an Agile issue management platform available to faculty and staff at Indiana University. JIRA allows teams to easily manage, track, and report issues throughout their lifecycle. JIRA is highly customizable, and can be tailored to fit any workflow you need.

Important:
Students do not have access to Jira software in a browser, but instead must use email to create and reply to issues.

Collaboration is a large point of emphasis in JIRA, including @mentioning (to draw a teammate's attention to a specific comment), formatted commenting, and sharing issues via email, all making work more visible.

Common JIRA use cases include software development, business issue tracking, feature implementation, bug tracking, and Agile project management (with JIRA Agile).

Jira works in conjunction with Bamboo, Crucible, and FishEye (also Atlassian products).

Features include a fast and smart editor, drag-and-drop file sharing, intelligent search, flexible notifications, integration with source code, integration with IU Enterprise Confluence, and granular permissions. View and update permissions are configurable. Projects may be viewable by many or viewable and editable by only a few.

For more about Jira at IU, see https://uisapp2.iu.edu/confluence-prd/pages/viewpage.action?spaceKey=TTS&title=Jira.

Access JIRA

Anyone can create or comment on a JIRA issue by sending email to an account associated with a JIRA project; however, managing items in a queue requires login access.

If you're IU faculty or staff, your JIRA account is automatically created the first time you access JIRA by logging into IU Login. Typically, students interact with JIRA via email.

If you intend to use JIRA for more than just sending occasional email or if you need to manage a queue, send a request for login access to the JIRA/Confluence mail queue, and provide the JIRA project(s) to which you need access. If you plan to work with a student project, have a faculty member send the request on your behalf.

Some projects permit viewing of issues, while others require certain group membership privileges. It's also possible to specify additional finer-grained permissions. Be sure to provide the type of access you need in your request. If you are not sure of the queue name, then specify what you do know about the queue (such as the email address used to submit items to the queue, names of the people you know to be associated with the queue, etc.).

When requesting a new JIRA project, specify a project name and project key (an acronym of up to 10 characters, alpha only). Most teams choose a product key that represents an acronym of their team or project's purpose.

UITS continues to add features and fix bugs, and encourages your comments and participation. Send requests to the JIRA/Confluence mail queue.

Institutional data in IU Enterprise JIRA

You may not use IU Enterprise JIRA to store institutional data classified as Critical or Restricted data. This includes, but is not limited to:

  • Social Security and driver's license numbers (even if considered PHI)
  • PINs and credit/payment card information (even if considered PHI)
  • Banking and student loan information
  • Student academic transcripts that contain student Social Security numbers
  • Passwords and passphrases
  • Financial account information
  • Information regulated by Export Control Laws, such as certain types of research or information about restricted items, technology, or software (see Office of Research Compliance: Export Control)

For more about classification levels for institutional data at IU, see Classification levels of institutional data. For more about working with sensitive institutional data at IU, see:

This is document baxx in the Knowledge Base.
Last modified on 2020-10-28 15:32:43.

Contact us

For help or to comment, email the UITS Support Center.