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
Cannot use left side menu when in Non-attributable emissions page
Steps to reproduce the behaviour:
On Non-Attributable Emissions page, click on menu listed on the left-hand side.
Screenshots:
Additional information:
Browser: Edge
Additional Context
User Story: As an Industry Reporter, I can fill out non-attributable emissions. Given that my answer to "did your non-attributable emissions exceeded 100 tCO2e" is yes, then I will see the activity name, source type, emission category, and gas type fields. Otherwise, I do not see these fields. #336
@shon-button I think this is related to an issue you already flagged, but I may be mis-remembering. Let me know if you think this is a separate issue and we should keep this bug ticket active!
patriciarussellCAS
changed the title
UAT Bug?- left side menu doesn't work when in Non-attributable emissions page
UAT Bug- Task list menu doesn't work when in Non-attributable emissions page
Dec 30, 2024
Describe the Bug:
Cannot use left side menu when in Non-attributable emissions page
Steps to reproduce the behaviour:
Screenshots:
Additional information:
Browser: Edge
Additional Context
User Story: As an Industry Reporter, I can fill out non-attributable emissions. Given that my answer to "did your non-attributable emissions exceeded 100 tCO2e" is yes, then I will see the activity name, source type, emission category, and gas type fields. Otherwise, I do not see these fields. #336
UAT TICKET: https://teams.microsoft.com/l/entity/com.microsoft.teamspace.tab.planner/mytasks?tenantId=6fdb5200-3d0d-4a8a-b036-d3685e359adc&webUrl=https%3A%2F%2Ftasks.teams.microsoft.com%2Fteamsui%2FpersonalApp%2Falltasklists&context=%7B%22subEntityId%22%3A%22%2Fv1%2Fplan%2FtGqZRZUMZk-c-CTHae_WtWUAGImJ%2Fview%2Fboard%2Ftask%2F764zrpauZkaZRE7Ya9TBqWUAJ6QT%22%7D
The text was updated successfully, but these errors were encountered: