Cell Editing Issues

​

Identify the Problem Type

• Cell won’t open editor?
  • Check read-only status (gray background)
  • Verify column permissions
  • Confirm user has edit rights
• Editor opens but save fails?
  • Check formula validation
  • Review field-level permissions
  • Inspect workflow restrictions
• Cell content disappears or changes unexpectedly?
  • Review dependent column logic
  • Check for formula overrides
  • Examine auto-population rules
• Link rendering breaks after edit?
  • Verify link column type configuration
  • Check for rich text field editing (known issue)

​

Check Read-Only Status

1. Identify read-only cells - Look for cells with gray background or cells that don’t respond to clicks
2. Verify column configuration - Check if the column is marked readOnly: true in your configuration:

{
  "columns": [
    {
      "id": "status",
      "header": "Status",
      "readOnly": true  // Prevents all editing
    }
  ]
}

3. Check automatic read-only fields - These fields are always read-only:
   • id (work item ID)
   • type (work item type)
   • project (project ID)
   • outlineNumber (hierarchical position)
   • Formula columns (automatically read-only)
   • Server-rendered columns (automatically read-only)

​

Resolve Permission-Based Restrictions

1. Enable permission checking - Ensure nextedy.risksheet.checkInstanceFieldPermissions=true is set in Project Administration > Permissions Management
2. Verify field-level permissions - In Polarion, check Administration > Project > Permissions > Work Items to ensure your role has edit rights for the specific field
3. Review workflow state restrictions - Some fields may be editable only in certain workflow states (e.g., editable in “draft” but locked in “approved”)

​

Fix Formula-Related Edit Failures

1. Check formula configuration:

{
  "columns": [
    {
      "id": "calculatedTitle",
      "formula": "item.severity + '-' + item.occurrence"
    }
  ]
}

2. Identify value mismatches - If a formula generates “High-Frequent” but the stored value is “High-Frequ” (truncated), permission validation may block the save
3. Manually correct mismatches - Update field values in Polarion to match formula output, or adjust formulas to match existing data
4. Review field length limits - After Polarion migrations, field length limits may have changed. Verify that formula outputs don’t exceed field capacity

​

Resolve Link Editing Issues

​

Links Break When Cells Are Edited

1. Disable automatic refresh - Add to your configuration:

{
  "global": {
    "refreshOnSave": false
  }
}

2. Manually refresh - After saving, use 🔄 Refresh Sheet from the toolbar instead of relying on automatic refresh
3. Preserve view position - As of version 25.5, cell selection and scroll position are preserved after save, reducing the impact of this issue

​

Rich Text Fields Lose Formatting

1. Use alternative column types - Configure as type: "text" instead of relying on Polarion’s rich text rendering
2. Edit in Polarion directly - Open the work item in Polarion’s native editor to preserve rich text formatting
3. Document the limitation - Rich text editing is not fully supported in RISKSHEET grids

​

Address Autocomplete and Suggestion Problems

1. Enable text field suggestions - Verify this global setting:

{
  "global": {
    "suggestTextFields": true
  }
}

2. Check link column configuration - For item link columns, ensure autocomplete is not blocked:

{
  "columns": [
    {
      "id": "linkedRequirement",
      "type": "itemLink",
      "canCreate": true  // Allows creating new items from autocomplete
    }
  ]
}

3. Verify query factory filters - Custom query filters may restrict available suggestions too aggressively

​

Handle Dependent Column Issues

1. Understand nested column behavior - Changing an item link auto-fills all sub-columns (e.g., Requirement.Status auto-fills when you select a requirement)
2. Review dependent enum configuration - Enum options refresh based on parent column values
3. Check undo/redo for dependencies - Undoing changes to parent columns also restores dependent column values

​

Verify Successful Resolution

1. Test cell editing - Click the previously problematic cell and verify the editor opens
2. Make a test edit - Enter a value and press Enter or Tab
3. Confirm save succeeds - Look for the success message and verify no error toasts appear
4. Check dependent columns - If editing a link column, verify nested columns auto-populate correctly

​

See Also

• Permission-Based Field Restrictions - Detailed permission troubleshooting
• Save Operation Failures - General save error resolution
• Rich Text Formatting Loss - Rich text editing limitations
• Configure Calculated Columns - Formula configuration
• User Roles and Permissions - Understanding permission model
• Configuration Properties Index - All configuration options