Project

General

Profile

Actions

Bug #28704

closed

Requirement Document : Requirement Type Not Removed from VOC Page After Deleting Requirement Branch from FSR Page

Added by Vani Kunnatheri 9 months ago. Updated 7 months ago.

Status:
Closed
Priority:
Medium
Assignee:
Start date:
07/24/2024
Due date:
% Done:

0%

Estimated time:
Steps To Reproduce:

1.Log into FST
2.Select FSR page
3.Select the Focus Element
4.Add a Function and Requirement against a safety goal.
5.Add a Requirement Branch.
6.Use a VOC Requirement.
7.Go to Requirement page and observe the Requirement type populated.
8.Go to FSR
9.Delete the Requirement branch which used VOC requirement.
10.Go to VOC page and observe the Requirement type of the same requirement.

MODULES:
FST
Build Cycle:
Cycle 2
Customer:
Issue Dependency:
Dev Commitment to Resolve in::
ISSUE TYPE:
NEW

Description

I added a requirement branch under an FSR function and used the VOC requirement. The 'Functional Safety' Requirement type was populated against the requirement in the VOC.
However, when I delete the requirement branch from the FSR page, the Requirement type is not getting deleted from the VOC page.


Files

FSR 1.png (57.9 KB) FSR 1.png Added Requirement branch with voc requirement Vani Kunnatheri, 07/24/2024 08:47 PM
FSR 2.png (104 KB) FSR 2.png Requirement type populated Vani Kunnatheri, 07/24/2024 08:48 PM
FSR 3.png (55.2 KB) FSR 3.png Deleted the Requirement branch Vani Kunnatheri, 07/24/2024 08:48 PM
FSR 4.png (93.7 KB) FSR 4.png Requirement type is still there Vani Kunnatheri, 07/24/2024 08:48 PM
Actions #2

Updated by User Admin 9 months ago

  • Status changed from New to Open
Actions #3

Updated by User Admin 9 months ago

  • Build Cycle changed from Cycle 1 to Cycle 2
Actions #4

Updated by Reng Raj 9 months ago

  • Assignee changed from chitra Kalangiam to Manoj Kumar
Actions #5

Updated by Reng Raj 9 months ago

  • Status changed from Open to Resolved
Actions #6

Updated by Vani Kunnatheri 8 months ago

  • Status changed from Resolved to Not Resolved
  • How do we missed in Testing ? set to Impact of another change

still able to see the requirement type as Functional safety in the VOC Requirement. Please check the patches

Actions #7

Updated by Manoj Kumar 8 months ago

  • Status changed from Not Resolved to Resolved
Actions #8

Updated by Vani Kunnatheri 7 months ago

  • Status changed from Resolved to Closed

verified and closed in cycle 4

Actions

Also available in: Atom PDF