Project

General

Profile

Actions

Bug #3139

closed

In phase Deadlines menu, after setting repeat limit not able to choose next priority from dropdown list , data is not available

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

Status:
Closed
Priority:
Medium
Assignee:
-
Start date:
10/30/2017
Due date:
% Done:

0%

Estimated time:
Steps To Reproduce:

1.Login to ewqims
2.Go to problem solver module
3.Problem solver setup→ Phase deadlines
4.Click on new
5.Select the req fields
6.Click on do you want set repeat limit checkbox
7.enter no of repeat eg:1
8.Click on next priority drop down list box
9.Observe result
10.Refer Screenshot

MODULES:
PS
Build Cycle:
Cycle 0
Customer:
Issue Dependency:
Dev Commitment to Resolve in::

Description

Observation :
#1 In phase Deadlines menu, after setting repeat limit not able to choose priority from next priority dropdown list box, data not available

#2 When no of repeat limit is set as 0, user is notified as saved successfully

#3 When only repeat limit is set , user tries to save must be notified as "choose next priority"

Expected : After repeat limit is set , next priority dropdown should display the other priorites available


Files

Actions #1

Updated by Anonymous over 7 years ago

  • Subject changed from In phase Deadlines, after setting repeat limit not able to view data in next priority dropdown box to In phase Deadlines, after setting repeat limit not able to choose priority from next priority dropdown box, data not available
  • Description updated (diff)
  • Steps To Reproduce updated (diff)
Actions #2

Updated by Anonymous over 7 years ago

  • Subject changed from In phase Deadlines, after setting repeat limit not able to choose priority from next priority dropdown box, data not available to phase
Actions #3

Updated by Anonymous over 7 years ago

  • Subject changed from phase to In phase Deadlines menu, after setting repeat limit not able to choose next priority from dropdown list , data is not available
  • Description updated (diff)
Actions #4

Updated by Anonymous over 7 years ago

  • Description updated (diff)
Actions #5

Updated by Anonymous over 7 years ago

  • Description updated (diff)
Actions #6

Updated by User Admin over 7 years ago

  • Status changed from New to Open
Actions #7

Updated by Radha Krishnan S over 7 years ago

  • Status changed from Open to In Progress
Actions #8

Updated by Anonymous over 7 years ago

  • Project changed from EwQIMS SP700 to EwQIMS SP730
Actions #9

Updated by Radha Krishnan S over 7 years ago

  • Assignee changed from Radha Krishnan S to Anonymous
Actions #10

Updated by Anonymous over 7 years ago

  • Status changed from In Progress to Fixed with Hotfix
Actions #11

Updated by Anonymous over 7 years ago

  • Status changed from Fixed with Hotfix to Resolved
Actions #12

Updated by Anonymous about 7 years ago

  • Status changed from Resolved to Yet to Verify
Actions #13

Updated by Anonymous about 7 years ago

  • Status changed from Yet to Verify to Not Resolved
Actions #14

Updated by Anonymous about 7 years ago

1. When priority is set as high in next priority should display both low and medium priority

2.Should not accept "0" in any format eg:00000 ,

Actions #15

Updated by Anonymous about 7 years ago

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

Updated by Radha Krishnan S about 7 years ago

Ensure that the next priority data that is expected to load is already mapped to an approach. In simple words, phase deadline should be already available for the priority so that it will be loaded in Next Priority.

Actions #17

Updated by Anonymous about 7 years ago

  • Status changed from In Progress to Resolved
Actions #18

Updated by Anonymous about 7 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF