Project

General

Profile

Actions
Copy link

Bug #2038

closed

LPA Schedule->Audit Assign Page-> Validation Message content is wrong

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

Status:
Closed
Priority:
Low
Assignee:
Nikhil d
Start date:
06/22/2017
Due date:
% Done:

100%

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.Change the auditor with conflict date and time
9.Click on Save button

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

Description

LPA schedule->Audit Assign->The validation message should be rewrite as "Conflicting schedule for Lead Auditor between date & time" when click on save button with conflict date and time between lead auditors

Files

A1.png (207 KB) A1.png Anonymous, 06/30/2017 12:30 PM
Actions
Copy link
 #1

Updated by Raja S almost 8 years ago

  • Subject changed from LPA Schedule->Audit Assign-> Validation Message content is wrong to LPA Schedule->Audit Assign Page-> Validation Message content is wrong
Actions
Copy link
 #2

Updated by Anonymous almost 8 years ago

  • Status changed from New to Open
Actions
Copy link
 #3

Updated by Bijoy P almost 8 years ago

  • Assignee changed from Bijoy P to Anonymous
Actions
Copy link
 #4

Updated by Anonymous almost 8 years ago

Waiting for Bijoy's Review

Actions
Copy link
 #5

Updated by Anonymous almost 8 years ago

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

Updated by Anonymous almost 8 years ago

The Expectation of the QA is not Clear

Actions
Copy link
 #7

Updated by Anonymous almost 8 years ago

  • Assignee changed from Anonymous to Bijoy P
Actions
Copy link
 #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
Copy link
 #9

Updated by Anonymous almost 8 years ago

  • Status changed from Open to In Progress
  • Assignee changed from Raja S to Nikhil d
  • Issue Dependency deleted (Dev Rejected : Need More Clarity )
Actions
Copy link
 #10

Updated by Nikhil d almost 8 years ago

  • Status changed from In Progress to Fixed in Dev
  • % Done changed from 0 to 100
Actions
Copy link
 #11

Updated by Anonymous almost 8 years ago

  • Status changed from Fixed in Dev to Resolved
Actions
Copy link
 #12

Updated by Anonymous almost 8 years ago

  • File A1.png A1.png added
  • Status changed from Resolved to Closed
Actions
Copy link

Also available in: Atom PDF