bcgov / bcgov/lcfs

LCFS - BUG TEST ENV - Unable to view transaction as an IDIR director

Open
#1,386 0 comments 0 reactions 0 assignees View on GitHub
bug Medium
Dominant language
Python
Stars
6
Forks
6
Avg merge
2d 7h
Merged PRs (30d)
87

Description

**Describe the Bug**
In the LCFS Portal Test Environment, IDIR directors are unable to view and accept Admin Adjustment transactions. While an IDIR analyst can successfully set up an admin adjustment, the transaction does not appear in the IDIR director's view for acceptance.

**Expected Behaviour**
- IDIR directors should be able to view and accept admin adjustments set up by IDIR analysts.
- The admin adjustment should appear in the director’s transaction list under the appropriate filter or category.

**Actual Behaviour**
- Admin adjustments set up by IDIR analysts are not visible to IDIR directors.
- As a result, IDIR directors are unable to accept these transactions.

**Implications**
- The inability for IDIR directors to view and accept admin adjustments disrupts the workflow for transaction approvals.
- This could lead to delays in the acceptance and finalization of admin adjustments.

**Steps To Reproduce**
Steps to reproduce the behaviour:
User/Role:

1. Log in as an IDIR analyst in the LCFS Portal Test Environment.
2. Set up an Admin Adjustment transaction.
3. Log in as an IDIR director.
4. Attempt to view and accept the admin adjustment transaction.
5. Observe that the transaction is not visible in the director's transaction list.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the workflow in the LCFS Portal Test Environment with an IDIR analyst and an IDIR director, following the listed admin-adjustment steps. Trace how the director’s transaction list is filtered and how acceptance permissions are checked. Done means a director can see and accept an analyst-created admin adjustment under the appropriate transaction filter.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
authorization, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.