Actions
Bug #14936
closedPM and Die: Team and Maintenance activity person--> When selecting and saving the different person for the activity, it displays the logged in person name in activity users field
Status:
Closed
Priority:
Medium
Assignee:
-
Start date:
11/18/2019
Due date:
% Done:
0%
Estimated time:
Steps To Reproduce:
1. Login as Maintenance Team activity person
2. Click on assigned WO
3. Click on Transaction code
4. Select the activity
5. Select different person for the activity
6. Click on save button
7. Observe the user field
MODULES:
TPM
Build Cycle:
Cycle 1
Customer:
Issue Dependency:
Dev Commitment to Resolve in::
Description
Issue 1: PM: Team--> When selecting and saving the different person for the activity, it displays the logged in person name in activity users field
Issue 2: When login as Supervisor for the Request to complete WO, it showing the logged in person name in completed activity user field
Files
| Issue 50.jpg (101 KB) Issue 50.jpg | |||
| Issue 51.jpg (39.6 KB) Issue 51.jpg | |||
| Issue 52.jpg (102 KB) Issue 52.jpg |
Updated by Kiruthika G over 5 years ago
- File Issue 52.jpg Issue 52.jpg added
- Description updated (diff)
Updated by Kiruthika G over 5 years ago
- Subject changed from PM: Team--> When selecting and saving the different person for the activity, it displays the logged in person name in activity users field to PM: Team and Maintenance activity person--> When selecting and saving the different person for the activity, it displays the logged in person name in activity users field
Updated by Kiruthika G over 5 years ago
- Subject changed from PM: Team and Maintenance activity person--> When selecting and saving the different person for the activity, it displays the logged in person name in activity users field to PM and Die: Team and Maintenance activity person--> When selecting and saving the different person for the activity, it displays the logged in person name in activity users field
Updated by Kiruthika G over 5 years ago
- Status changed from Resolved to Not Fixed with Hotfix
Updated by Anonymous over 5 years ago
- Status changed from Not Fixed with Hotfix to Resolved
Actions