Patron Notices (UXPROD-18)

[UXPROD-1582] Reorganize patron notice settings Created: 15/Mar/19  Updated: 16/Sep/20  Resolved: 06/Sep/19

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Patron Notices

Type: New Feature Priority: P4
Reporter: Darcy Branchini Assignee: Darcy Branchini
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to UICIRC-202 Reorganize patron notice settings Draft
Epic Link: Patron Notices
Development Team: Vega
PO Rank: 30
PO Ranking Note: More important once notice partials are built (if they are). It's my belief that all of settings should be reviewed and revisited after functionality for v1 has been addressed. It's suffering from a lack of UI consistency, patterns and organization.
Rank: Chalmers (Impl Aut 2019): R4
Rank: Chicago (MVP Sum 2020): R2
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R4
Rank: FLO (MVP Sum 2020): R2
Rank: GBV (MVP Sum 2020): R2
Rank: hbz (TBD): R2
Rank: Hungary (MVP End 2020): R2
Rank: Lehigh (MVP Summer 2020): R4
Rank: TAMU (MVP Jan 2021): R2
Rank: U of AL (MVP Oct 2020): R4

 Description   

Reorganize patron notice settings so that the structure is clearer to the end user and easier to use. Instead of separate lines for templates, policies and formats under circulation, I suggest the following reorganization:

  • Circulation
    • Patron notices
      • Formats (when feature is completed - UXPROD-1532 Draft )
      • Partials (if/when feature is completed - UXPROD-1583 Draft )
      • Policies
      • Templates

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