Project

General

Profile

Actions

Usability #5091

closed

Function Analysis: Alignment was not correct for the Maximized Requirement Tree while Opening the Menu again

Added by Anonymous about 7 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Medium
Assignee:
-
Start date:
03/12/2018
Due date:
% Done:

100%

Estimated time:
Steps To Reproduce:

1.Goto EwQIMS
2.Login as VDA Module User
3.Click on PI Tab and Select the PI
4.Click on Design VDA Tab and Select the Function Analysis Menu
5.Click on Maximize Button for the Requirements Tree
6.Again Click on Design VDA Tab and Select the Function Analysis Menu
7.Also Click on Failure Analysis Menu
8.Observe the Results for both the Menus

MODULES:
VDA
Build Cycle:
Cycle 2
Customer:
Issue Dependency:
Dev Commitment to Resolve in::

Description

In Function Analysis, Maximize the Requirement Tree window and again Open the Function Analysis from the Design VDA now the Alignment will not be good and the three Windows was merged and shown as single window without the BOM and Table/Tree View windows.
Same Issue was coming for the Failure Analysis Menu.


Files

Actions #1

Updated by Shankar Narayanan about 7 years ago

  • MODULES VDA added
  • MODULES deleted (AQUAPRO)
Actions #2

Updated by User Admin about 7 years ago

  • Status changed from New to Open
Actions #3

Updated by Anonymous about 7 years ago

  • Tracker changed from Bug to Usability
Actions #4

Updated by Anonymous about 7 years ago

  • % Done changed from 0 to 10
Actions #5

Updated by Anonymous about 7 years ago

  • Status changed from Open to Resolved
Actions #6

Updated by Shankar Narayanan about 7 years ago

  • Status changed from Resolved to Not Resolved
Actions #7

Updated by Anonymous about 7 years ago

  • Assignee changed from Anonymous to Anonymous
  • % Done changed from 10 to 100
Actions #8

Updated by Anonymous about 7 years ago

  • Status changed from Not Resolved to In Progress
Actions #9

Updated by Anonymous about 7 years ago

  • % Done changed from 100 to 0
Actions #10

Updated by Anonymous about 7 years ago

  • % Done changed from 0 to 100
Actions #11

Updated by Anonymous almost 7 years ago

  • Status changed from In Progress to Resolved
Actions #12

Updated by Anonymous almost 7 years ago

  • Status changed from Resolved to Closed

This Issue was Verified in Cycle-7 and the Issue was Fixed so the QA Team is Closing this Issue.

Actions

Also available in: Atom PDF