Project

General

Profile

Actions
Copy link

Bug #5395

closed

EFC Tree - Element that is flowed down without any function/requirement/ Failure is not displayed in EFC Tree

Added by Shankar Narayanan about 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Medium
Assignee:
Reng Raj
Start date:
04/03/2018
Due date:
% Done:

100%

Estimated time:
Steps To Reproduce:

1.Select failure Tree
2.Allocate element without function/requirement/ Failure
3.Select EFC Tree
4.Observe the result

MODULES:
RFD
Build Cycle:
Cycle 0
Customer:
Issue Dependency:
Cycle 1
Dev Commitment to Resolve in::
810

Description

Element that is flowed down without any function/requirement/ Failure is not displayed in EFC Tree

Files

Download all files
2018-04-03 Test EFCTree.jpg (66 KB) 2018-04-03 Test EFCTree.jpg Shankar Narayanan, 04/03/2018 06:59 PM
2018-04-18 EFCTree JS Error.png (54.8 KB) 2018-04-18 EFCTree JS Error.png Shankar Narayanan, 04/18/2018 12:37 PM
Actions
Copy link
 #1

Updated by Smitha V about 7 years ago

  • Status changed from New to Open
Actions
Copy link
 #2

Updated by Smitha V about 7 years ago

  • Assignee changed from Smitha V to Anonymous
Actions
Copy link
 #3

Updated by User Admin about 7 years ago

  • Status changed from Open to In Progress
  • Dev Commitment to Resolve in: set to 750

Since this will affect the VDA Functionality this will fix in SP750

Actions
Copy link
 #4

Updated by Shankar Narayanan about 7 years ago

In Cycle 6, when clicking on the Context arrow, system displays a JS Error.

Actions
Copy link
 #5

Updated by User Admin about 7 years ago

  • Status changed from In Progress to TBD
Actions
Copy link
 #6

Updated by User Admin about 7 years ago

  • Status changed from TBD to Future Release
  • Dev Commitment to Resolve in: changed from 750 to 810

Will moving this to future release as we have to release SP735 on 19042018 and not yet received the file

Actions
Copy link
 #7

Updated by Shankar Narayanan almost 7 years ago

  • Project changed from EwQIMS SP735 to SP810 - QA build
Actions
Copy link
 #8

Updated by User Admin almost 7 years ago

  • Build Cycle changed from Cycle 3 to Cycle 0
Actions
Copy link
 #9

Updated by Anonymous over 6 years ago

  • Issue Dependency set to Cycle 1
Actions
Copy link
 #10

Updated by Anonymous over 6 years ago

  • Status changed from Future Release to Resolved
  • % Done changed from 0 to 100
Actions
Copy link
 #11

Updated by Anonymous over 6 years ago

  • Assignee changed from Anonymous to Reng Raj
Actions
Copy link
 #12

Updated by Anonymous over 6 years ago

  • Status changed from Resolved to Closed

Issue Fixed in Cyc-2, Hence closed the Issue

Actions
Copy link

Also available in: Atom PDF