Fees/Fines (UXPROD-792)

[UXPROD-1247] Fees/Fines Settings - Q1 2019 release updates Created: 22/Oct/18  Updated: 31/Aug/21  Resolved: 15/Mar/19

Status: Closed
Project: UX Product
Components: Fees/Fines
Affects versions: None
Fix versions: Q1 2019
Parent: Fees/Fines

Type: New Feature Priority: P2
Reporter: Holly Mistlebauer Assignee: Holly Mistlebauer
Resolution: Won't Do Votes: 0
Labels: feesfines, mandatory, resourceaccess
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Epic Link: Fees/Fines
Front End Estimate: Large < 10 days
Front End Estimator: Holly Mistlebauer
Front-End Confidence factor: Low
Back End Estimate: Large < 10 days
Back End Estimator: Holly Mistlebauer
Development Team: UNAM
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R1
Rank: GBV (MVP Sum 2020): R1
Rank: Lehigh (MVP Summer 2020): R1
Rank: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): R1

 Description   

This feature does not need to be ranked--this is a holding place for changes to Fees/Fines Settings that are needed for the Q1 2019 release and will be done regardless of rankings.



 Comments   
Comment by Theodor Tolstoy (One-Group.se) [ 25/Oct/18 ]

Cate BoeremaHolly Mistlebauer Chalmers have not discussed this ticket, it has been automatically set for Go-live. This is not the only one. Does this not take away some of the purpose with these rankings?

Comment by Theodor Tolstoy (One-Group.se) [ 25/Oct/18 ]

We think it is better practice to not have the rankings carried over. Then the Jira tickets are more easy to find and discuss. Also, they are not automatically showing in the "Remaining not in Q4 " column that people might look in order to get a picture of the prospects for a Go live after the Q4 release.

Comment by Holly Mistlebauer [ 15/Mar/19 ]

There ended up being no fixes needed for Q1 2019.

Generated at Fri Feb 09 00:13:59 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.