Fees/Fines (UXPROD-792)

[UXPROD-387] Future Fees/Fines: Automated bulk overdue fine correction Created: 21/Mar/18  Updated: 06/Dec/22

Status: Draft
Project: UX Product
Components: Fees/Fines
Affects versions: None
Fix versions: None
Parent: Fees/Fines

Type: New Feature Priority: TBD
Reporter: Holly Mistlebauer Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: Unassigned-from-Holly, feesfines, resourceaccess
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: JPEG File Automated Bulk Overdue Fine Correction.jpg    
Potential Workaround: Holly: This was always viewed as a future feature. No workaround is needed.
Epic Link: Fees/Fines
Front End Estimate: XL < 15 days
Front End Estimator: Holly Mistlebauer
Front-End Confidence factor: Low
Back End Estimate: XXL < 30 days
Back End Estimator: Holly Mistlebauer
Estimation Notes and Assumptions: This is post-v1 so not much work analysis has been done on this.
Development Team: Vega
Kiwi Planning Points (DO NOT CHANGE): 1
PO Rank: 0
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R2
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R5
Rank: FLO (MVP Sum 2020): R4
Rank: GBV (MVP Sum 2020): R4
Rank: Grand Valley (Full Sum 2021): R4
Rank: hbz (TBD): R4
Rank: Hungary (MVP End 2020): R4
Rank: Lehigh (MVP Summer 2020): R4
Rank: Leipzig (Full TBD): R4
Rank: Leipzig (ERM Aut 2019): R5
Rank: TAMU (MVP Jan 2021): R2
Rank: U of AL (MVP Oct 2020): R5

 Description   

We need a way to correct overdue fine errors that occur due to calendar errors (e.g. snow days).

Attached image contain mock-up and in-progress requirements for this feature.



 Comments   
Comment by Cate Boerema (Inactive) [ 24/Apr/18 ]

Just switching this to Open, as it make things easier for sorting and such. I might change it so the "To Do" column is only fed by Open items, as I'm finding the fact that multiple statuses can reside here a bit challenging.

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