Add a perm to govern fund rollover

Bug #1977761 reported by Tiffany Little
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Wishlist
Unassigned

Bug Description

Right now the perm that governs whether or not a user can do year end rollover on funds is just ADMIN_FUND. Because year end rollover is really hard to roll back once you've done it, it would be useful to limit who has the ability to do the once a year fund rollovers.

We would like to see a new permission called something like ADMIN_FUND_ROLLOVER that can govern whether or not the user can do the fund rollover for the year.

Revision history for this message
Tiffany Little (tslittle) wrote :
tags: added: pullrequest
Revision history for this message
Jennifer Pringle (jpringle-u) wrote :

Having this perm separate is a great idea!

Changed in evergreen:
status: New → Confirmed
Changed in evergreen:
importance: Undecided → Wishlist
tags: added: permissions
Revision history for this message
Lindsay Stratton (lstratton) wrote :

Tested in Chrome, https://tiffany-master.gapines.org/

Login as Acquisitions profile user br1breid/barbarar1234, BR1
Confirmed that user account does not have ADMIN_FUND_ROLLOVER permission
On opening Acq Admin > Fund Administration "Fiscal Propagation and Rollover" not clickable

Login as Acquisitions Administrator profile br1lfarrell/lindaf1234, BR1
Confirmed that user account does have ADMIN_FUND_ROLLOVER permission
On opening Acq Admin > Fund Administration "Fiscal Propagation and Rollover" available
Able to complete year end rollover

Revision history for this message
Lindsay Stratton (lstratton) wrote :

I have tested this code and consent to signing off on it with my name, Lindsay Stratton and my email address, <email address hidden>

tags: added: signedoff
Changed in evergreen:
milestone: none → 3.10-beta
Galen Charlton (gmc)
Changed in evergreen:
assignee: nobody → Galen Charlton (gmc)
Revision history for this message
Galen Charlton (gmc) wrote :

Pushed to master for inclusion in 3.10, along with follow-ups to avoid surprises in upgraded databases, to add release notes, and to enforce the permission at the API level. Thanks, Tiffany and Lindsay!

Changed in evergreen:
status: Confirmed → Fix Committed
assignee: Galen Charlton (gmc) → nobody
Changed in evergreen:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.