| Jira Review and Prioritization | Please review your existing Jira issues and programming needs for April and May.
- Speak with your supervisor or other team members regarding future ITS programming needs. For example, if you need something in preparation for April, May, or June, it is time to submit your requests for prioritization. If you have multiple ITS programming needs for a month, rank them amongst your team.
- The leadership team will meet Tuesday, March 25 for review. We realize this is a short turn-around time. Below is a list of upcoming scheduled meetings:
- April 22 at 9:30 a.m.
- May 27 at 9:30 a.m.
- June 24 at 9:30 a.m.
- Bugs and projects are generally prioritized first.
- Those items that “would be nice to have” will depend on the impact to students and other campus partners as well as developer availability.
| | Prioritizing Monthly Jiras
- If REG Jira: send Jessica Alberhasky and Sara Morelli an email with your request for prioritization. Most Jira issues in the REG project should already have a fix version and discussion with ITS has already taken place. We will advocate for your requests with ITS.
- If REGISTRAR Jira: apply fix version “APR_2025” or “MAY_2025”.
- If you’ve discussed the Jira or request with Becky, change Jira status to “Ready”.
- If you are not sure if a Jira request can be prioritized, change the status to “Discussion Need” and contact Sara M. or Jessica will bring these to Becky weekly. Generally, these meetings occur Wednesdays at 11 a.m.
| | | Project Updates |
| Project |
Developer |
Comments |
|
Accessibility Updates
|
All developers
|
Nearly all accessibility issues in MyUI have been resolved. Next Becky will work on prioritizing MAUI focus areas.
|
|
Course Offering Allocations
|
Martin Happ |
The allocations project is wrapping up. Martin is currently working on enhancements to the Section Heatmap Report that will be linked off of from the Time/Location panel in MAUI to improve accessibility to departmental administrators. |
|
Curriculum Administration
|
Chris Petta
Pragati Tanwar
|
Multi-year project to record curriculum requirements in MAUI. Drafting project charter with initial ITS development to begin later this spring.
|
|
Final Exam Duration Support
|
Canan Tapia
|
A new exam length field is being created to allow flexibility in final exam durations. |
|
Office 365/Ad Astra
|
Chris Petta
|
Chris is working on the new integration between MAUI and Ad Astra. Chris and Renee are wrapping up testing.
|
|
Transcript and Verification Enhancement Project
|
Pragati Tanwar
|
Currently work on enhancements to the MAUI/MyUI Verifications and automating the transcript workflow integration with MAUI.
|
|
Program of Study Sync Enhancements
|
Canan Tapia
|
Jolene and Jessica met with Canan and Becky to discuss overall themes and scenarios when the Admission's POS and Student Program of Study fails to sync. More discussion on next steps will be occurring this week.
|
|
Professional Licensure Attestation
|
Canan Tapia
|
Testing project to notify students when their program of study does not meet licensure requirements in their residing state.
|
| | | Steps in Creating a Jira Request | JIRA Guidelines and Best Practice Complete Document
Items Needed in a Jira Request
- State the problem first (if Bug)
- State what you need or want to happen
- Then, provide any additional information
- Location of MAUI or MyUI panel with URL and "breadcrumbs" or path to specific page
- Screenshots and student or course examples are helpful
- Warning or wording updates- need the text when the request is submitted
- Is there a specific deadline that this change is needed by?
Tip: Explain it as though that person knows nothing about the request. It will help the developer and will allow us to refer to the Jira request for documentation
Reference related requests. Typing this Jira number in the description, summary, or comment areas will automatically hyperlink to that Jira.
Consulting and Design: We need more information to move this Jira request forward. Please see the comments. | | | Jira Requests to Review |
- Grab-bag Jira Request - Review priority label (Very High, High, Medium, Low). These are items that any developer can grab to work on if they have time. Developers will use the priority to help determine which Jira to grab next. If these requests are needed by a specific date, please include that in the description field.
- "In Review – Older than 2 weeks" - Please review that filter below and let us know if there are extenuating circumstances that keep the Jira request from moving to production.
| | | Tips from AIS Developer! |
- If you are currently testing a Jira request and need changes made by a developer, comment and move the status from "In Review" back to "To Do". This action will automatically assign it back to the developer to work on.
- If you've been working with a developer, have a Jira request assigned to you as "In Review", and you are unable to test it right away, please add a comment to the Jira and tag (@name) the developer. This is helpful if you are out of the office for a while. They will try to do the same.
- If you are working on a Jira request and have a quick question, need guidance to keep things moving, or need a batch job pushed, please feel free to reach out via Microsoft Teams Chat. Comments on a Jira request should be utilized for information on programming changes, documentation, and testing results. If a decision is made in Teams, those notes should be summarized in the corresponding Jira request for documentation.
| | | |
