bcgov / bcgov/foi-flow

Linked Requests - AXIS sync to update linked requests displaying incorrectly

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

Description

**Describe the bug in current situation**

When a request has linked requests (i.e., has been synced with AXIS and populated the linked requests), the AXIS sync banner is being displayed. When seeing what needs to be synced, it is saying that no linked requests are in AXIS (which is incorrect), and it needs to be synced (see image below). When you do sync with AXIS, the linked requests in Mod remain unchanged.

This is occurring on MAG-2023-31229 and HSG-2023-31231
![image.png](https://images.zenhubusercontent.com/636ac0ea6aad1b5dd6b181ee/c277bd63-f186-4724-931c-1a81c82226b2)

As per standard AXIS sync functionality, the AXIS sync should only show up when there is data that is inconsistent between the request in AXIS and Mod, and then show the fields and data that must be synced to update.

**Link bug to the User Story**
#1191

**Impact of this bug**
Low

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

**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

Start by tracing the AXIS sync handling for linked requests described in issue #3936, using MAG-2023-31229 and HSG-2023-31231 as examples and reviewing user story #1191. Done means the sync banner appears only when linked-request data differs between AXIS and Mod, and syncing updates the linked requests correctly.

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
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.