You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you generate a treasury report, it does not always include recent changes and it is not clear how long you need to wait for changes to be incorporated. This makes it confusing to know if you are getting up to date information when you pull the treasury report
Current State
When you generate a treasury report, it send an email almost immediately, but recent changes are often not reflected.
Expected State
No changes to the user workflow when you click the "Send Treasury Report by Email" button
One the email the user receives with the treasury report link, a new line should display beneath "Your treasury report can be downloaded here" - the new line should say "This treasury reports includes valid uploads as of DD/MM/YYYY HH:MM:SS" - the date and time should reflect the date/time stamp from database of the last valid upload.
Implementation Plan
Relevant Code Snippets
No response
The text was updated successfully, but these errors were encountered:
ClaireValdivia
changed the title
[Issue]: Treasury Report does not reflect recent changes
[Issue]: Add timestamp messages to Treasury Report front end
Nov 19, 2024
ClaireValdivia
changed the title
[Issue]: Add timestamp messages to Treasury Report front end
[Issue]: Add timestamp messages to Treasury Report email
Dec 4, 2024
Why is this issue important?
When you generate a treasury report, it does not always include recent changes and it is not clear how long you need to wait for changes to be incorporated. This makes it confusing to know if you are getting up to date information when you pull the treasury report
Current State
When you generate a treasury report, it send an email almost immediately, but recent changes are often not reflected.
Expected State
Implementation Plan
Relevant Code Snippets
No response
The text was updated successfully, but these errors were encountered: