Project

General

Profile

Actions

Bug #3862

closed

Benchmarking->New Benchmark-> Unassigned "Context" is displayed when selecting expectation category from list

Added by Raja S over 7 years ago. Updated about 7 years ago.

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

100%

Estimated time:
Steps To Reproduce:

1.Login as BOSS module admin
2.Click on Interested Party Expectations tab
3.Click on "Benchmarking" link from menu
4.Click on New button
5.Select expectation category from list
6.Select "Context" from list
7.Click on Save button
8.Go to benchmark listing page
9.Select the created expectation category by clicking on respective checkbox
10.Click on Delete button
11.Again click on "New" button
12.Select the same expectation category again
13.Observe the result

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

Description

Benchmarking-> New Benchmark-> Unassigned "Context" is displayed automatically when selecting expectation category from list. The context is already been assigned for respective expectation category and its deleted from benchmarking listing page.

But the problem happened only when the user selecting this removed expectation category again on new benchmarking page.

Actions #1

Updated by Ramesh Sanker over 7 years ago

  • Assignee changed from Ramesh Sanker to Anonymous
Actions #3

Updated by Anonymous over 7 years ago

  • Status changed from New to Open
Actions #4

Updated by Anonymous over 7 years ago

  • Status changed from Open to Fixed in Dev
  • % Done changed from 0 to 100
Actions #5

Updated by Anonymous over 7 years ago

  • Status changed from Fixed in Dev to Resolved
Actions #6

Updated by Raja S over 7 years ago

  • Status changed from Resolved to Not Resolved
Actions #7

Updated by Anonymous over 7 years ago

  • Status changed from Not Resolved to Fixed in Dev

Change in " BO_DeleteBenchMark " stored procedure.

Actions #8

Updated by Anonymous about 7 years ago

  • Status changed from Fixed in Dev to Resolved
Actions #9

Updated by Raja S about 7 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF