[UXPROD-3964] Rollover Cash Balance During FYRO Created: 10/Jan/23  Updated: 30/Nov/23  Resolved: 28/Mar/23

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Orchid (R1 2023)

Type: New Feature Priority: P2
Reporter: Thomas Trutt Assignee: Dennis Bridges
Resolution: Done Votes: 0
Labels: communitycontrib
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File Screenshot 2023-01-24 at 8.00.04 AM.png     PNG File image001.png     PNG File image002.png    
Issue links:
Defines
is defined by MODFISTO-371 Add support to rollover cash balance ... Closed
is defined by MODFISTO-373 Add migration script to support cache... Closed
is defined by UIF-440 Add Rollover budget Cash balance sett... Closed
is defined by UIF-441 Render new listbox to be able to roll... Closed
Development Team: Thunderjet
PO Rank: 0
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R1

 Description   

Overview:

Funds for FY2023 showing the available balance moved forward.  So, when invoices are processed against the purchase orders that were encumbered at the end of FY22 they are being charged twice.  We need FYRO updated to move the cash balance forward or at least to have the option to use cash balance instead of available balance.

Scope:

TBD

Approach:

User is able to choose to rollover either available amount OR cash balance (Use select list rather than check boxes)
User can specify to rollover this value as allocation OR transfer
If user chooses roll as allocation and user also checks rollover allocation then this additional value is added to allocation value of new budget.

Additional information:

See diagram at https://miro.com/app/board/uXjVOkZO8Qk=/?moveToWidget=3458764544073973477&cot=14{}



 Comments   
Comment by Ann-Marie Breaux (Inactive) [ 10/Jan/23 ]

Hi Dennis Bridges There was no dev team on this bug, so I added Tjet

Comment by Dennis Bridges [ 11/Jan/23 ]

Just noting here that I have changed this into a feature so we can clarify requirements and define an approach for adding these additional rollover options.

Comment by Ann Crowley [ 19/Jan/23 ]

Dennis Bridges - I really view this as a bug.  Is this going to be fixed before we need to run FYRO in June 2023.

Comment by Debra Howell [ 19/Jan/23 ]

Dennis Bridges Cornell needs this before FYRO this year. What is the dev path if you have changed it to a New Feature instead of a Bug (I agree with Ann - this really seems like a bug)?

Comment by Dennis Bridges [ 20/Jan/23 ]

Ann Crowley and Debra Howell I can appreciate that but it was never identified as a requirements to rollover cash balance. I think this may have gone unnoticed because we didn't actually show a cash balance originally, we only had available amount. So when it came to rollover that was the only option we provided. Cash balance was added later.

Is it correct that you will be rolling over in June and thus running the Orchid release?

There is only one sprint remaining before the the Orchid code freeze so it could be very difficult and risky to try and design and implement a solution for Orchid. However, I will review with the team on Tuesday to see if we can identify a potential solution. Once I have little more information we can discuss the possibilities.

Comment by Ann Crowley [ 23/Jan/23 ]

Dennis Bridges - If this isn't fixed we will just be closing the year and having to do things manually.  Rolling forward the available balance and not the cash balance charges the fund twice for every encumbered purchase order at the time of FYRO - which is why this is a bug.  I had to go in manually make adjustments on the carryforward balances to correct this for the last fiscal year.

Comment by Anya [ 23/Jan/23 ]

Support: would like to weigh in that this should be treated as a higher priority - Money in all forms should be counted as part of FY rollover - this put an undue amount of manual labor on the FY rollover process. 

 

Could we please have a projected release target for this?

Comment by Dennis Bridges [ 26/Jan/23 ]

Over the last few days we have been able to refine and estimate an approach for meeting this requirement. As a result i have added the Orchid release tag. To review the data flow you can see the acquisitions knowledge MIRO board at https://miro.com/app/board/uXjVOkZO8Qk=/?moveToWidget=3458764544073973477&cot=14. For more details on how a user will accomplish this please review the user stories linked to this feature. In particular UIF-440 Closed .

Comment by Khalilah Gambrell [ 13/Feb/23 ]

Hey Dennis Bridges  - can this feature's status move to In Review or Closed?

Comment by Dennis Bridges [ 28/Mar/23 ]

All stories resolved for release in Orchid

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