Bug #6318
closedRegression - Document viewer: Advanced search option.
0%
1)Login to ewqims application
2)Select APQP module
3)Select the project
4)Click on document viewer
5)Observe the result
Description
Document viewer: Advanced search option.
Please find the document for reference.
Could not download from, chrome in doc viewer
Files
| document viewer.docx (191 KB) document viewer.docx | |||
| doc viewer.png (34.2 KB) doc viewer.png |
Updated by Anonymous almost 7 years ago
- File doc viewer.png doc viewer.png added
- Description updated (diff)
Updated by Anonymous over 6 years ago
- Project changed from SP810 Dev Build to SP810 - QA build
- Build Cycle changed from Cycle 3 to Cycle 1
Updated by Varadharaj S over 6 years ago
- Status changed from Open to Resolved
1) After entering incorrect data and clicking on search button – No response
Need “No data found” alert. - fixed
2) When the search option filter is selected as % completed then it allows entering the alphabetic values also, it should allow only accepting numeric value - Its combination search filed so restriction to numeric not possible
3) After selecting the filters in advanced search and reset filter is needed instead of No filter.
Because the name advanced search will not be displayed after the selection of any filter - fixed
4) When the cursor is placed in the deliverable name it shows clickable option - since its a label it shows pointer
cursor , its not a bug ewims css follows this ( more detail contact anil)
5) “Advanced search” option is not looking in the button view- This is not a issue , anil proposed this design
Updated by Anonymous over 6 years ago
- Subject changed from Document viewer: Advanced search option. to Regression - Document viewer: Advanced search option.
Updated by Anonymous over 6 years ago
- Status changed from Resolved to Not Fixed with Hotfix
1) After entering incorrect data and clicking on search button – No response
Need “No data found” alert. - Not fixed
When entering the aqua output document name it is not showing the correct results
Updated by Varadharaj S over 6 years ago
- Status changed from Not Fixed with Hotfix to Resolved
Updated by Anonymous over 6 years ago
- Status changed from Resolved to Not Resolved
Updated by Varadharaj S over 6 years ago
- Status changed from Not Resolved to Resolved
Updated by Anonymous over 6 years ago
- Status changed from Resolved to Fixed with Hotfix
Updated by Anonymous over 6 years ago
- Status changed from Fixed with Hotfix to Resolved