Fees/Fines
(UXPROD-792)
|
|
| 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: | feesfines, loans, resourceaccess | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
| Potential Workaround: | Supervisor logs in and performs a regular override. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Epic Link: | Fees/Fines | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Development Team: | Vega | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Kiwi Planning Points (DO NOT CHANGE): | 1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| PO Rank: | 49 | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R4 | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R2 | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Duke (Full Sum 2021): | R3 | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R2 | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R3 | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: MO State (MVP June 2020): | R2 | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R4 | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
Current situation or problem: In scope
Out of scope Use case(s)
Proposed solution/stories
Links to additional info
Questions
|
| Comments |
| Comment by Holly Mistlebauer [ 04/Sep/20 ] |
|
Darcy Branchini, Emma Boettcher, Cate Boerema: Here is the new feature for permission escalation. I have assigned it to myself, but I think it should be assigned to Darcy since Vega is working on it. Darcy, is that o.k. with you? |
| Comment by Cate Boerema (Inactive) [ 07/Sep/20 ] |
|
Thanks for filing this, Holly Mistlebauer. I wonder if we should just have a feature for "Permission escalation for override" and include in that feature (1) spike for deciding on an approach (2) stories implementing in various places. I know that deciding on the approach has already begun and I think we should bring that to a good stopping point (ideally with an approach decided). But I am not sure we should prioritize implementing it right now. I'd like to see how the feature is ranked first. I think the PO for the feature should be someone who is responsible for the user workflows that make use of it. Probably Emma Boettcher or Holly Mistlebauer, not Darcy Branchini. Thoughts? |
| Comment by Darcy Branchini [ 10/Sep/20 ] |
|
I agree Cate Boerema with both of your suggestions above. |
| Comment by Holly Mistlebauer [ 12/Sep/20 ] |
|
Cate Boerema: Just to make this clear to myself...
One question:.
|
| Comment by Cate Boerema (Inactive) [ 14/Sep/20 ] |
|
This sounds like a good approach to me, Holly.
I think the bulk of the work for permission escalation will be designing and developing the general mechanism. Wiring it into the individual features can be prioritized at the story level and we POs can touch base with the RA SIG on priorities when we get close to development. |
| Comment by Darcy Branchini [ 15/Sep/20 ] |
|
Cate Boerema Holly Mistlebauer, FYI I also outlined next steps, but they are detailed next steps and I did it in
|
| Comment by Holly Mistlebauer [ 10/Jan/22 ] |
|
Not sure why this has been assigned to me, but I will leave it as is for now.... |