Hi all,
I would like to check if anyone has experienced a similar behavior or if this should be raised as a potential bug.
According to IFS documentation and standard behavior:
- Pool Task: the first user who accepts the task becomes the owner; the task is removed from the pool for all other users.
- Pool‑Keep: multiple users can accept the task; individual assignments are created and the task remains visible in the pool until explicitly removed.
I am currently working on IFS Cloud 25R2 using the Maintenance MWO mobile app, and I am facing an issue where the Pool‑Keep functionality does not seem to work when a Resource Group (resource demand) is specified on the Work Task. In detail, when I define a Resource Group on the task, then select Transfer to Mobile and choose Pool – Keep Task, the task is correctly shown in the app as “resource group specified”, but as soon as one technician accepts the task, it immediately disappears from Pool Work and is no longer visible to other technicians. Additionally, the Pool‑Keep icon does not appear on the task preview, which suggests that the task is effectively behaving like a standard Pool Task. I have tested the same scenario without specifying a Resource Group, and in that case Pool‑Keep works as expected: the task remains in the pool, the Pool‑Keep icon is visible, and at completion the system asks whether to keep the task in the pool.
Based on IFS documentation and standard descriptions, Pool‑Keep should work specifically when tasks are distributed to a Resource Group.
Can this be a configuration issue, or should we raise a support ticket as this appears to be a potential bug?
