Actions
Bug #30116
openConsolidated TARA / CAL Determination page - Previously added requirement appears as a new branch instead of being linked to the existing record
Start date:
01/30/2025
Due date:
% Done:
0%
Estimated time:
Steps To Reproduce:
1.Log into cybersecurity
2.Go to consolidated Tara
3.add a new record, enter the asset, violation security, damage scenario, and threat scenario first
4.Add the requirement
5.Refresh the page and observe
MODULES:
CYBER SECURITY
Build Cycle:
Cycle 4
Customer:
Issue Dependency:
Dev Commitment to Resolve in::
How do we missed in Testing ?:
Description
In the consolidated TRA page or in the Asset identification and CAL determination page , added a new record, entered the asset, violation security, damage scenario, and threat scenario first, then the requirement for the same record without refreshing the page. After refreshing the page, the requirement appears as a new branch, even though it was added for the same record
Files
Actions