Project

General

Profile

Actions

Bug #2031

closed

LPA Schedule->Audit Assign Page->Assignd lead auditor name displaying even after selecting the auditor from list

Added by Raja S almost 8 years ago. Updated almost 8 years ago.

Status:
Closed
Priority:
Medium
Assignee:
Start date:
06/22/2017
Due date:
% Done:

0%

Estimated time:
Steps To Reproduce:

1.Login as module admin
2.Expand administrator tab
3.Click on LPA Schedule link
4.Select Layer and year
5.Click on Create schedule/Reschedule button
6.Click on any tentative audit
7.Click on Lead auditor selection icon
8.Select any auditor from list by clicking on selection icon

MODULES:
AUDITPRO
Build Cycle:
Cycle 1
Customer:
Issue Dependency:
Dev Rejected : Need More Clarity
Dev Commitment to Resolve in::

Description

Lead auditor selection field-> The dropdown list always showing the assigned auditor name even after selecting the lead auditor name until clicks on outside the page

Actions #1

Updated by Raja S almost 8 years ago

  • Subject changed from LPA Schedule->Audit Assign Page->Assign lead auditor name displaying even after selecting the auditor from list to LPA Schedule->Audit Assign Page->Assignd lead auditor name displaying even after selecting the auditor from list
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 Anonymous almost 8 years ago

Waiting for Bijoy's Review

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 Raja S
  • 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

We already discussed about this with QA and identified as Not an Issue.

We added this item into the MVC Conversion Plan.

Actions #10

Updated by Anonymous almost 8 years ago

  • Status changed from Open to Closed
Actions

Also available in: Atom PDF