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
Describe the Bug
In the Allocation Agreement view table of the compliance report, the CI (Carbon Intensity) number is currently displaying with too many decimal places. It should be limited to only two decimal places for clarity and consistency. The current behavior is displaying many fractional digits, which is not necessary and can be confusing for users.
Expected Behaviour
The CI (Carbon Intensity) number in the Allocation Agreement view table should be limited to only two decimal places (e.g., 45.67).
Actual Behaviour
The CI number is currently displayed with excessive decimal places, making the values appear cluttered and hard to interpret and is inconsistent with our use of 2 decimal places across the application.
Implications
Displaying too many decimal places can create confusion and reduce the clarity of the data in the Allocation Agreement view.
Users may struggle to accurately interpret the CI number, impacting their ability to review compliance reports effectively.
Steps To Reproduce
Steps to reproduce the behaviour:
User/Role: BCeID
Navigate to the Allocation Agreement view table in the compliance report.
Observe the CI (Carbon Intensity) number displayed with many decimal places.
Note that the CI value should be limited to only two decimal places.
The text was updated successfully, but these errors were encountered:
Describe the Bug
In the Allocation Agreement view table of the compliance report, the CI (Carbon Intensity) number is currently displaying with too many decimal places. It should be limited to only two decimal places for clarity and consistency. The current behavior is displaying many fractional digits, which is not necessary and can be confusing for users.
Expected Behaviour
The CI (Carbon Intensity) number in the Allocation Agreement view table should be limited to only two decimal places (e.g., 45.67).
Actual Behaviour
The CI number is currently displayed with excessive decimal places, making the values appear cluttered and hard to interpret and is inconsistent with our use of 2 decimal places across the application.
Implications
Steps To Reproduce
Steps to reproduce the behaviour:
User/Role: BCeID
The text was updated successfully, but these errors were encountered: