Usability #4073
closedRegression - Calendar:When the Project name is too large then after selecting the project.it will not allow to deselect the project
0%
1)Login to EWQIMS application
2)Select APQP module
3)Click on Activites Tab
4)Select Calendar Menu
5)Select the Project(Lengthy name)
6)Observe the result(Try Close deselect)
Description
1)Calendar:When the Project name is too large then after selecting the project.it will not allow to deselect the project
2)Calendar: Data displaying in the calendar is not user specific.When Clicking on the task listed in the calendar it redirects to the deliverable list without the specification of the selected deliverable
3)In Social media Page,Clicking on deliverable link will not redirect to the my deliverable list page.
Files
Updated by Anonymous over 7 years ago
- Build Cycle changed from Cycle 1 to Cycle 0
Updated by Anonymous about 7 years ago
- Description updated (diff)
- Priority changed from Low to Medium
Updated by User Admin about 7 years ago
- Status changed from Open to Future Release
Updated by Anonymous almost 7 years ago
- Project changed from EwQIMS SP730 to SP810 - QA build
- Issue Dependency set to SP730
- Dev Commitment to Resolve in: set to 810
Updated by Anonymous over 6 years ago
- Subject changed from Calendar:When the Project name is too large then after selecting the project.it will not allow to deselect the project to Regression - Calendar:When the Project name is too large then after selecting the project.it will not allow to deselect the project
Updated by Anonymous over 6 years ago
1)Calendar:When the Project name is too large then after selecting the project.it will not allow to deselect the project - Fixed
2)Calendar: Data displaying in the calendar is not user specific.When Clicking on the task listed in the calendar it redirects to the deliverable list without the specification of the selected deliverable - Not Fixed
3)In Social media Page,Clicking on deliverable link will not redirect to the my deliverable list page - Fixed
Updated by Varadharaj S over 6 years ago
- Status changed from Future Release 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