Based on the symptoms you’re describing - especially the timing after a project configuration update - this is almost certainly a workflow configuration issue. Here’s a comprehensive solution addressing all the key areas:
Workflow Transitions:
First, export your workflow XML and verify the complete transition definition. The snippet you showed is incomplete - you need to check for conditions, validators, and post-functions:
<transition id="approve_transition" from="pending_manager" to="approved">
<conditions>
<condition class="com.polarion.workflow.CustomCondition"/>
</conditions>
<validators>
<validator class="com.polarion.workflow.FieldValidator"/>
</validators>
</transition>
Any condition or validator that fails will silently block the transition.
Role Permissions:
Verify in Administration > Roles that the manager role has these permissions:
- Can modify work items in this status
- Can perform workflow actions
- Can edit LiveDoc sections
Also check Project Properties > Permissions to ensure managers aren’t restricted at the project level.
LiveDoc Locking:
For the 5 locked documents, you have two options:
- Contact the users to close their LiveDocs
- Use Admin override: Administration > Documents > Locked Documents > Select items > Force Unlock
Be cautious with force unlock as it may cause users to lose unsaved changes.
Admin Override for Stuck Items:
For the 18 non-locked requirements, you can manually transition them:
- Navigate to Administration > Work Items
- Select the stuck requirements
- Use Bulk Edit > Change Status > Select “approved”
- This bypasses the workflow and forces the status change
Root Cause Investigation:
Check your Polarion logs immediately after attempting an approval:
tail -f /opt/polarion/data/logs/polarion.log | grep -i workflow
Look for validation errors, permission denials, or custom function failures.
Configuration Comparison:
Since this started after a project config update, use Administration > Project Configuration > Compare to review what changed. Focus on:
- Custom field definitions referenced in workflow conditions
- Workflow XML modifications
- Role assignment changes
Most likely, your workflow has a condition checking a custom field that was modified in the config update, causing silent validation failures. Identify and update the condition to match the new field configuration.
After fixing the root cause, test with a single requirement before processing all stuck items in bulk.