Project

General

Profile

Actions

Bug #28155

closed

Requirements Document - Deleted the 'Reviewed Requirement' from the 'Requirements' and could not add a new Requirement to the deleted requirement branch in the 'VOC'. (Refer Description)

Added by Gopinath Ramamoorthy 11 months ago. Updated 10 months ago.

Status:
Closed
Priority:
Medium
Start date:
05/21/2024
Due date:
% Done:

0%

Estimated time:
Steps To Reproduce:

1. Log in to the RFD.
2. Select the Requirements Document.
3. Review the Requirement delete the Requirement from 'Requirements' and add a new Requirement in the deleted branch.
4. Allocate the Element to the Requirement and delete the Requirement in 'Requirements'.
5. Add the Requirement in the VOC at the deleted branch.

MODULES:
RFD
Build Cycle:
Cycle 1
Customer:
Issue Dependency:
Requirements Document
Dev Commitment to Resolve in::

Description

1. Deleted the 'Reviewed Requirement' from the 'Requirements' and could not add a new Requirement to the deleted requirement branch in the 'VOC'.
2. Allocated the element to the Requirement and deleted the Requirement from 'Requirements'. After adding a new Requirement in the deleted branch, the allocated element from the deleted Requirement is displayed for the new Requirement.


Files

75.png (170 KB) 75.png Gopinath Ramamoorthy, 05/21/2024 09:20 AM
Actions #2

Updated by User Admin 11 months ago

  • Status changed from New to Open
Actions #3

Updated by Reng Raj 11 months ago

  • Assignee changed from chitra Kalangiam to Navyasri Govindu
Actions #4

Updated by Shankar Narayanan 10 months ago

1. Deleted the 'Reviewed Requirement' from the 'Requirements' and could not add a new Requirement to the deleted requirement branch in the 'VOC'. - FIXED
2. Allocated the element to the Requirement and deleted the Requirement from 'Requirements'. After adding a new Requirement in the deleted branch, the allocated element from the deleted Requirement is displayed for the new Requirement. - As Discussed with Biju and Chitra, this needs Marks support and due to multiple dependencies and impacts, this cannot be handled now. So, closing this issue

Actions #5

Updated by Navyasri Govindu 10 months ago

  • Status changed from Open to Resolved
Actions #6

Updated by Gopinath Ramamoorthy 10 months ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF