Project

General

Profile

Actions

Bug #7479

closed

DFMEA : Mark & Move Branches is throwing an "Object reference set to an instance" message

Added by Anonymous over 6 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Medium
Start date:
08/01/2018
Due date:
% Done:

0%

Estimated time:
Steps To Reproduce:

1.Open the Browser
2.Enter the URL
3.Enter the Username and Password
4.Click on Login Button
5.Click on Module icon
6.Click on AQuAPro
7.Click on Main Menu
8.Select the PI -> Open DFMEA Document
9.Select any Branch and Select Mark to Move Branches option by Selecting any of the Column Cell from the Requirement Column onwards
10.Select one Empty Branch and Select Move Marked Branches
11.Observe the Results

MODULES:
AQUAPRO
Build Cycle:
Cycle 1
Customer:
Issue Dependency:
Dev Commitment to Resolve in::

Description

In DFMEA Document, by Mark Branch & Move Branch in an empty branch is throwing an "Object reference set to an instance" message


Files

Actions #1

Updated by User Admin over 6 years ago

  • Status changed from New to Open
Actions #2

Updated by Sugesh g pillai over 6 years ago

  • Status changed from Open to In Progress
Actions #3

Updated by Sugesh g pillai over 6 years ago

  • Status changed from In Progress to Resolved
  • Assignee changed from Sugesh g pillai to Anonymous

Fixed and patch moved to build on 9/26

Actions #4

Updated by Anonymous over 6 years ago

This Issue is Not Resolved and its Replicating Now also so Changing the Status as Not Resolved on 27.09.2018

Actions #5

Updated by Sugesh g pillai over 6 years ago

Fixed another (different) Mark & Move Branches that is throwing an "Object reference set to an instance" message. In this case, right-clicking on a cell that is contained in a lowest branch that does not go down to the cell’s branch or the parent branch is not allowed. The example Sugesh showed me was a Design Requirement Usage branch that was marked and being moved by right-clicking on another Design Requirement Usage cell, but the cell was contained in a lowest branch that only went down to Design Function Group, which is two branch levels above Design Requirement Usage. The code has been changed to display the “Move not allowed” message in this case. Note that if you select a Design Function in the Design Function Usage branch, this will create a Design Function Usage branch and then the move can be done (since the parent branch exists). Or, if a Design Requirement is selected in the empty Design Requirement Usage branch causing a Design Requirement Usage branch to be created, then the move can also be done (since the branch exists). Will be available for build on 10/08/2018

Actions #6

Updated by Sugesh g pillai over 6 years ago

  • Status changed from Not Resolved to Resolved
  • Assignee changed from Anonymous to Sugesh g pillai
Actions #7

Updated by Anonymous over 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF