Project

General

Profile

Actions

Bug #5212

closed

Structure Analysis in Process VDA: The Operations and its 4m was loading for the Last Segment and its not loading for the Mapped Segment

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

Status:
Closed
Priority:
High
Assignee:
-
Start date:
03/22/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 Process VDA Tab and Select the Structure Analysis Menu
5.Right-Click and Create Multiple Segment in the Segment Popup
6.Choose one Segment and Create Single/Multiple Operations and 4M by clicking on the Operations and 4M Icons
7.Now again Select the Structure Analysis Menu the System will Hang
8.Refresh the URL and Select the same PI and Select the same Structure Analysis Menu
9.Now Without choosing the Segment Click on Done Button
10.Observe the Results

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

Description

In Structure Analysis, by simply clicking Done Button without choosing the Segment on the Popup it showing the Operations and its 4m for the Last Segment but actually it want to show for the Mapped Segment only.

EX: Segment named as "Seg 1, Seg 2, Seg 3"
Selected Segment is "Seg 1"
Click on Operations Icon and Create Operations as "OP 001, OP002, OP 003"
Click on 4m Icon for the each Created Operations and Map all the 4m as "Man, Machine, Material, Method"
Now it will be display as "Seg 1 -> OP 001(all 4m), OP 002(all 4m), OP 003(all 4m)" but it will display as "Seg 3 -> OP 001(all 4m), OP 002(all 4m), OP 003(all 4m)" by reloading the Menu


Files

Actions #1

Updated by Anonymous about 7 years ago

  • Tracker changed from Unit Level and Cosmetic Issues to Bug
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

  • Status changed from Open to Resolved
  • Assignee changed from Anonymous to Anonymous
  • % Done changed from 0 to 100

Had some technical issue and now it's resolved

Actions #4

Updated by Anonymous about 7 years ago

  • Status changed from Resolved to Not Resolved

This Issue was Verified in Cycle-4 and the Issue was not Fixed so the QA Team is Changing the Status into Not Resolved.

Actions #5

Updated by Anonymous about 7 years ago

  • Status changed from Not Resolved to Resolved

Updated by Anonymous about 7 years ago

This Issue was Verified in Cycle-6 and the Issue was not Fixed so the QA Team is Changing the Status into Not Resolved.

Actions #7

Updated by Anonymous about 7 years ago

Resolved On 12/04/2018

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 Shankar Narayanan almost 7 years ago

  • Status changed from Resolved to Closed

Closed in SP750 Cycle 7.

Actions

Also available in: Atom PDF