Using the Torus Triage Board

Do you need immediate assistance?

<aside> 🔥 If something is blocking your ability to use Torus, or if something is keeping students from being able to successfully navigate courses, don’t stand on formality.  We need to know right away! Email [email protected] or click “Tech Support” in the upper right hand corner of Torus as shown in the screen shot below.

</aside>

An image showing the tech support link in the upper right-hand corner of each Torus screen

Contents 🦉

Document Purpose and Intended Audience

This document is intended for any member of the Torus Community who is interested in reporting bugs or requesting features. Hopefully this will be a good resource for you in learning how to use the Torus Triage Board to accomplish this, but please don’t hesitate to contact Torus’s Product Manager if you need a hand.

Who is the Product Manager?

Amanda Buddemeyer is the Technical Product Manager for Torus. I am in charge of Torus’s roadmap, which means I want to hear from you about the Torus features and bugs that are important to you.

How can I provide feedback?

Is there information that you wish were in this document that is missing? Is something explained in a way that you find confusing? Do you just want to tell me that my document is awesome? Email me at [email protected].

You are also welcome to provide feedback on the Torus Triage Board itself (see Customizing Your Torus Triage Board).

Product Manager Amanda Buddemeyer

What is the Torus Triage Board?

A screen shot of the Torus Triage Board in Jira

The Torus Triage Board is the single source of truth for Torus feature requests and bug reports.  It exists is Jira, but you do not need a Jira login to use it - it is accessible to the public.   This document assumes that you have no previous experience with Jira at all. All instructions and screen shots will assume the user does not have a Jira login.

You can access the Torus Triage board here:

https://eliterate.atlassian.net/jira/software/c/projects/TRIAGE/issues

Issue Types

External Contributors

• Bugs report an aspect of the application that does not work as intended
• Feature Requests ask for a new element or function for the application that doesn’t currently exist

Internal Use Only

• Epics are created by the product team and establish categories of issues around a common theme.
• Chores are used only by the internal software development team.

A screen shot showing the Issue Type filter and all of the possible issue types on the Torus Triage Board