Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TFRS - Notification link for supplemental requested broken after creation of a draft supplemental report #2461

Open
justin-lepitzki opened this issue Jul 25, 2023 · 2 comments
Labels
Bug Something isn't working Main release For immediate release into production when ready Medium Medium priority

Comments

@justin-lepitzki
Copy link
Collaborator

Describe the Bug
Compliance report not loading when trying to access the report through the notifications page. This bug only occurs when the IDIR user requests a supplemental report (status: Supplemental Requested) and the BCeID user has created a draft supplemental.

Expected Behaviour
Clicking on the notification link for a compliance report (e.g., "Compliance Report for 2022 Supplemental Requested") should take you to the latest version of the 2022 report (draft supplemental, if created; otherwise the submitted report)

Actual Behaviour
The report is not loading when the BCeID user clicks on the notifications link (within the notifications page). Again, this is a specific edge case that only occurs when the IDIR user has requested a supplemental report (status: Supplemental Requested) and the BCeID user has created a draft supplemental. The report is still accessible through the 'Compliance & Exclusion Reports' main page.

Implications
Report fails to load and is causing confusion for suppliers in trying to access their reports.

Steps To Reproduce
Steps to reproduce the behaviour:

  • have a submitted compliance report
  • BCeID user has in-app notifications turned on for 'Supplemental Requested'
  • IDIR user requests supplemental report by clicking on the 'Request Supplemental' button within a submitted compliance report
  • BCeID user navigates to the compliance report through the 'Compliance & Exclusion Reports' page and creates a draft supplemental report.
  • BCeID user then goes to their in-app notifications and clicks on the link to the report from the in-app notification (i.e., "Compliance Report for YYYY Supplemental Requested").
  • The report will fail to load and their will be errors in the inspect console.

Example Report in Test:

Screenshot of console error:
Screenshot 2023-07-25 notification link broken.png

Screenshot of notifications page where the link to access is located:
Screenshot 2023-07-25 notification link broken notifications page.png

@justin-lepitzki justin-lepitzki added Bug Something isn't working High High priority ticket but not critical at this time Main release For immediate release into production when ready Medium Medium priority and removed High High priority ticket but not critical at this time labels Jul 25, 2023
@justin-lepitzki
Copy link
Collaborator Author

justin-lepitzki commented Jul 25, 2023

This may be a larger issue where the system is not redirecting to the latest version of a report when clicking on links that have URLs associated with a previous versions of a report.

Another example of a similar error of a report failing to load when using an older version URL, but in the dev environment: credit transaction ID# 1049 is a reduction of 6,169 credits from acceptance of a 2023 compliance report. When clicking on the transaction entry on the credit transactions page, the report fails to load. A supplemental report for 2023 has been created and submitted (ID# 1023). When the user clicks on the reduction transaction entry, the system tries to load the report (ID# 1020) but fails to redirect to the latest version of the report (ID# 1023); it gets stuck loading.

Screenshot 2023-07-25 152741.png

@prv-proton
Copy link
Collaborator

Hey team! Please add your planning poker estimate with Zenhub @AlexZorkin @jig-patel @prv-proton

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Main release For immediate release into production when ready Medium Medium priority
Projects
None yet
Development

No branches or pull requests

2 participants