bcgov / tfrs

Transportation Fuels Reporting System
Apache License 2.0
23 stars 40 forks source link

TFRS - Exclusion Report Changelog UI - Complete the Exclusion Reports, Report History Tab Changelog #2013

Open kcabhar opened 1 year ago

kcabhar commented 1 year ago

Description Currently the Exclusion Report Changelog shows the changes made to a supplemental report but used back-end code language in the UI for labeling these changes. This is confusing for TFRS users.

We need to update this view to match the newly created Compliance Report Changelog UI. Use the same style of component and logic to implement the exclusion report changelog.

Use the similar style of this wireframe: https://preview.uxpin.com/f727aca33d80cb2a585f76fe43cc583c2f548b07#/pages/119620817?mode=fm

Expected Behaviour When completed, the changes should be shown in the UI to make it easy to view and understand for the user. Essentially replacing the backend code wording with plain language and presenting it in a more appropriate manner.

Actual Behaviour Currently, the “Report History” Tab under an Exclusion Report lists the changes however, they are listed in code.

Implications This is difficult for users to understand and decipher.

Steps to reproduce the behaviour: User/Role: IDIR

  1. Go to 'TFRS dashboard in TEST and click on the “Compliance & Exclusions Reports” Tab.'
  2. Click on 'Organizations and filer for “South Coast Fuels” and open the 2022 Exclusion Report and navigate to the “Report History” tab.'
  3. Scroll down to 'To “Changelog for Exclusion Report for 2022 -- Supplemental Report #1”.'
  4. See error – You will note that under the part that says “Exclusion Report for 2022 -- Supplemental Report #1” the change shows changes presented in code.
airinggov commented 1 year ago

the exclusion report changelog UI can probably follow the same design as the compliance report changelog UI https://preview.uxpin.com/f727aca33d80cb2a585f76fe43cc583c2f548b07#/pages/119620817?mode=fm

kcabhar commented 1 year ago

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