Project

General

Profile

Actions

Bug #1979

closed

In Audit type Screen when clicked on assign routes it goes on and off

Added by Anonymous almost 8 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Low
Assignee:
-
Start date:
06/21/2017
Due date:
% Done:

100%

Estimated time:
Steps To Reproduce:

1)Access the link http://192.168.100.249/EwQIMS1
2)login to the module
3)click on module setup
4)click on audit type
5)fill all the mandatory fields
6)click on assign routes
7)a new window will open in which able to see all the escalation Routes
8)which goes off for a while and it comes back

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

Description

in Audit type after entering the audit type code will be generated automatically and when clicked on "assign routes" a new window will open in which able to see all the routes coming from suite of a while it displays and it goes off and it comes again.


Files

Route1.png (154 KB) Route1.png Anonymous, 08/04/2017 01:50 PM
Route2.png (161 KB) Route2.png Anonymous, 08/04/2017 01:50 PM
Actions #1

Updated by Anonymous almost 8 years ago

  • Subject changed from in Audit type Screen when clicked on assign routes it goes on and off to In Audit type Screen when clicked on assign routes it goes on and off
Actions #2

Updated by Anonymous almost 8 years ago

  • Status changed from New to Open
Actions #3

Updated by Bijoy P almost 8 years ago

  • Assignee changed from Bijoy P to Anonymous
Actions #4

Updated by Bijoy P almost 8 years ago

Need to fix

Actions #5

Updated by Anonymous almost 8 years ago

  • Issue Dependency set to Waiting for Bijoy's Review
Actions #6

Updated by Anonymous almost 8 years ago

The Expectation of the QA is not Clear

Actions #7

Updated by Anonymous almost 8 years ago

  • Assignee changed from Anonymous to Bijoy P
Actions #8

Updated by Bijoy P almost 8 years ago

  • Assignee changed from Bijoy P to Anonymous
  • Issue Dependency changed from Waiting for Bijoy's Review to Dev Rejected : Need More Clarity

The Expectation of QA is not Clear.

We need clarity while reporting the issue and expecting the following points :

1)Need Screenshots as mandatory
2)Comparewith Current result and Expected result while proposing any changes
3)Need Consistency in bug reporting
4)Required new category as suggestion, if it is new (Now QA is considering suggestion as bug)

This will help to save the Dev team analysing time.

Please do the needful

Actions #9

Updated by Anonymous almost 8 years ago

  • Status changed from Open to In Progress
  • Assignee changed from Anonymous to Anonymous
  • Issue Dependency deleted (Dev Rejected : Need More Clarity)
Actions #10

Updated by Anonymous almost 8 years ago

  • Assignee changed from Anonymous to Nikhil d
Actions #11

Updated by Anonymous over 7 years ago

  • Status changed from In Progress to Fixed in Dev
  • Assignee changed from Nikhil d to Anonymous
  • % Done changed from 0 to 100
Actions #12

Updated by Anonymous over 7 years ago

  • Status changed from Fixed in Dev to Resolved

Moved to Retest

Updated by Anonymous over 7 years ago

Still there is issue

Actions #14

Updated by Anonymous over 7 years ago

  • Status changed from Not Resolved to Resolved
Actions #15

Updated by Anonymous over 7 years ago

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

Updated by Anonymous over 7 years ago

  • Status changed from Fixed with Hotfix to Closed
Actions

Also available in: Atom PDF