Actions
Bug #2694
closedIn find and replace : when replacing invalid data in Target date column the Alert message is not valid
Status:
Closed
Priority:
Medium
Assignee:
-
Start date:
08/29/2017
Due date:
% Done:
0%
Estimated time:
Steps To Reproduce:
1.Login to aquapro
2.Select any PI item.
3.select any dfmea document.
4.right on the Target date column >rightclick and select find and replace >fill the find as "08/21/2017" and fill the replace value example "commondo"
5.dialog window appear
6. search it
7.Find and replace dailog appear -apply and ok
8.observe result.
MODULES:
AQUAPRO
Build Cycle:
Cycle 0
Customer:
Issue Dependency:
700
Description
find and replace in date column : when replacing some in Target date it Alert message is not valid.
Files
Updated by Jacqueline Antonette almost 8 years ago
- Status changed from Open to Fixed with Hotfix
Updated by Jacqueline Antonette almost 8 years ago
- Status changed from Fixed with Hotfix to Resolved
Updated by User Admin almost 8 years ago
- Status changed from Resolved to Not Resolved
Updated by User Admin almost 8 years ago
- Subject changed from In find and replace : when replacing some in Target date it Alert message is not valid. to In find and replace : when replacing invalid data in Target date column the Alert message is not valid
Updated by User Admin almost 8 years ago
- Status changed from Not Resolved to In Progress
Updated by Sugesh g pillai almost 8 years ago
- Status changed from In Progress to Resolved
Date search will ignore filter conditions like match with, start with etc and do only = (equal to).
This is updated in 7.0.0.1
Updated by Sugesh g pillai almost 8 years ago
- Assignee changed from Sugesh g pillai to Anonymous
Updated by User Admin almost 8 years ago
- Status changed from Reopen to Fixed with Hotfix
Updated by User Admin almost 8 years ago
- Project changed from EwQIMS SP700 to EwQIMS SP710
- Status changed from Fixed with Hotfix to Resolved
- Build Cycle changed from Cycle 8 to Cycle 0
- Issue Dependency set to 700
Moving from SP700
Updated by Anonymous almost 8 years ago
- Status changed from Resolved to Closed
This Issue was Verified & Closing in SP710.
Actions