bcgov / bcgov/foi-flow

Wrong Name Associated with Comment/Action

Open
#4,949 0 comments 0 reactions 0 assignees View on GitHub
bug low priority
Dominant language
Python
Stars
8
Forks
2
Avg merge
14h 34m
Merged PRs (30d)
46

Description

**Describe the bug in current situation**

On OOP-2023-33415 in PROD, the comment from 2023 Dec 29, 12:29 PM has the wrong user being listed as taking the action.

The user that took the extension was Nina. However, Debby is listed as taking the extension, seven days after reassigning the request, and no longer touching the request.

Unable to reproduce issues in Test. Thought it may be an issue about syncing with AXIS, and tried a variety of scenarios (similar to the audit trail in the 'Comments' tab on the request), and could not reproduce this issue. Need to investigate logs and see if there were any anomalies.

**Link bug to the User Story**

**Impact of this bug**
Describe the impact, i.e. what the impact is, and number of users impacted.

**Chance of Occurring (high/medium/low/very low)**

**Pre Conditions: which Env, any pre-requesites or assumptions to execute steps?**

PROD

**Steps to Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

**Actual/ observed behaviour/ results**

**Expected behaviour**
A clear and concise description of what you expected to happen. Use the gherking language.

**Screenshots/ Visual Reference/ Source**
If applicable, add screenshots to help explain your problem. You an use screengrab.

Contributor guide

Open the contributing guide

Research direction

No file or test is named. Start by reviewing the PROD logs and the audit trail in the request's Comments tab, then investigate whether AXIS synchronization explains the actor recorded for the December 29 extension. Done means identifying why Debby was listed instead of Nina and documenting a reproducible verification or regression check.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.