-
Notifications
You must be signed in to change notification settings - Fork 1
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
289 allocation of emissions bugs #2562
Conversation
f2f5bd2
to
e4d0d87
Compare
chore: fix textarea field
eb7d9c1
to
b67a8e7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work! This makes things much more smooth & no extraneous data is getting into the database.
One thing I'd check with PO / BA is the behaviour of the "Save" button when 100% of emissions are not yet allocated. There is a message at the bottom that says you cannot "save & continue" without 100% allocation, which is good & that button is greyed out. However, the "Save" button looks live but when clicked, nothing gets saved. If the preference of the PO/BA is to not allow saving data at all until 100% of emissions are allocated then this button should also be greyed out, if they want to be able to save the data as-is at that point, then we'll need to wire that button to actually save when clicked.
^ That can be handled in another ticket when we get clarity on what the expectation is there around saving data when 100% of emissions have not been allocated.
Screenshot:
@@ -11,7 +11,7 @@ export default async function FacilityEmissionAllocationPage({ | |||
}) { | |||
const orderedActivities = await getOrderedActivities(version_id, facility_id); | |||
const initialData = await getEmissionAllocations(version_id, facility_id); | |||
|
|||
console.log(initialData); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
left over debugging line
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops, I just went ahead and merged it immediately after approval. My bad. I'll just take this out in my current PR
Ahh, that might have been it. I do forget to update that field sometimes and jump right into allocating. I'll check it again during our QA session this afternoon, thanks! |
✏️ Notes
Fixed in reporting buttons fixes #2567 (also applied to this branch):
🐛 Issues addressed:
Backend:
reporting.models.report_product_emission_allocation\allocated_quantity
fieldmax_digits
from 10 to 20Frontend:
Totals in tCO2e\Total emissions attributable for reporting
is of inconsistent width with the rest of the page.emission_category_name
🔬 Local Testing:
Operation 3
, click buttonStart
Expected results:
Allocation of Emissions
page displays under stepReport Information
, taskAllocation of Emissions
Production Data
display as expected in product categoryTotal Emissions
Totals in tCO2e\Total emissions attributable for reporting
displays total as expectedSave
is enableSave and Continue
is disabledAll emissions must be allocated to 100% before saving and continuing
Expected results:
Totals in tCO2e
Save
Expected results:
Expected results:
Save and Continue
is enabledAll emissions must be allocated to 100% before saving and continuing
Save and Continue
Expected results:
Additional Reporting Data