ITS Updates and Reminders

Office of the Registrar

Monthly Prioritization

Now is the time to review your development needs for January and February. As a reminder, our prioritization process for ITS development has changed. See the November 24th Jira Prioritization Process and ITS Updates message for more information.

Submit your Jira requests by December 19th with all required information for prioritization (see below) and reach out to Jessica and Sara to share the urgency, impact, and overarching issue so we can help advocate for your needs. This information helps determine priority amongst all requests from our office. With the winter holidays, development time is limited to allow staff to use their vacation time. High impact or urgent requests will be prioritized.

Requests will not be moved forward to ITS without the required information for prioritization.

Required Information for Prioritization

  • Priority (Blocker, Very High, High, Medium, Low)
    • Requests may be repriortized in the next sprint when comparing needs across the office
  • Urgency: Add notes in Description field to explain impact and timeline to production
  • Screenshots or mock-ups (with alt text)
  • Examples (student IDs, course, etc.) for testing so developers can test before moving back to us for further testing
  • Navigation – URL/path/ “breadcrumbs” to issue
  • Link to recent related/similar Jiras

Priority Guidelines

Very High Priority

Must-do items that are urgent, broadly impactful, and often tied to external requirements.

Consider when:

  • There’s a regulatory or compliance deadline.
  • Affects all or most students in critical ways.
  • Significantly reduces staff workload or eliminates manual processes.
  • ITS is already engaged or coordination is critical.
  • Major inefficiencies or errors are present.

High Priority

Important initiatives that improve operations or student experience, but may not be urgent.

Consider when:

  • Strong policy driver or internal deadline.
  • Broad impact (e.g., college or department level).
  • Moderate staff time savings or improved accuracy.

Medium Priority

Useful enhancements or fixes that can wait or be bundled with other work.

Consider when:

  • No external pressure but aligns with best practices.
  • Limited impact to small groups.
  • Modest time savings or incremental improvement.

Low Priority

Nice-to-have items or ideas that may not justify the effort right now.

Consider when:

  • No compliance or policy driver.
  • Minimal or unclear impact.
  • Little time saved or few users benefit.
  • Cosmetic or marginal improvement.

Project Updates

Project 

Developer(s)

Update

Accessibility Updates

All developers

MyUI is nearly completely remediated. MAUI is about 95% remediated. 

Curriculum Administration

Chris Petta

Pragati Tanwar

Continuing to build a module to create curriculum by associating courses with requirements. 

Migrate Developer Forms to Form2 App

Brian Smith

Due to accessibility, the existing Forms app has been replaced with a new Forms2 app. Work is now underway to move the Prerequisite Permission to Enroll form.

Syllabi Information

Dave Martin

Continuing to add additional fields in Course Library and Offerings Planner to support the Board of Regents Syllabi Posting and Notification of Students on Class Content Policy

Program of Study Sync Enhancements

Canan Tapia

Developing logic that determines the primary program of study in MAUI.