Actions
Bug #16330
closedResources Allocation: It allowing to allocate two person for the WO in resources allocation screen
Status:
Closed
Priority:
Medium
Assignee:
-
Start date:
04/17/2020
Due date:
% Done:
0%
Estimated time:
Steps To Reproduce:
1. Login EwQIMS as TPM Module administrator
2. Click on Equipment and select activity with max people needed option as "1"
3. Click on PM Supervisor calendar
4. Click on Assign PM button
5. Click on Resources allocation menu
6. Assign the User more than 2
7. Observe the alert message
MODULES:
TPM
Build Cycle:
Cycle 1
Customer:
Issue Dependency:
Dev Commitment to Resolve in::
Description
Resources Allocation: When the Max people needed option is "1", in resources allocation, it allows resources to assign "3" user for the WO. When tries to assign one more user, it shows error like "User already assigned"
Files
Updated by Kiruthika G almost 5 years ago
- Status changed from Resolved to Not Resolved
Updated by Anonymous almost 5 years ago
- Status changed from Not Resolved to Resolved
Updated by Kiruthika G almost 5 years ago
- File Resources allocation-maxpeople.jpg Resources allocation-maxpeople.jpg added
- Status changed from Resolved to Not Resolved
Updated by Anonymous almost 5 years ago
- Status changed from Not Resolved to In Progress
Updated by Anonymous almost 5 years ago
- Status changed from In Progress to Resolved
Updated by Kiruthika G almost 5 years ago
- File 20200508_145630.mp4 20200508_145630.mp4 added
- Subject changed from Resources Allocation: When the Max people needed option is "1", in resources allocation, it allows resources to assign "3" user for the WO. When tries to assign one more user, it shows error like "User already assigned" to Resources Allocation: It allowing to allocate two person for the WO in resources allocation screen
- Status changed from Resolved to Not Resolved
Updated by Anonymous almost 5 years ago
- Status changed from Not Resolved to In Progress
Updated by Anonymous almost 5 years ago
- Status changed from In Progress to Resolved
Updated by Kiruthika G almost 5 years ago
- Status changed from Resolved to Fixed with Hotfix
Updated by Kiruthika G almost 5 years ago
- Status changed from Fixed with Hotfix to Closed
Actions