Skip to main content

​
Version 24.5.0 Date Format Regression

Nextedy RISKSHEET version 24.5.0 introduced a timezone handling fix that inadvertently broke date column saving when the format property was configured. This issue was identified and resolved in subsequent patch releases. Symptoms:
  • Save operations fail for date columns with custom format property
  • Error messages referencing date validation or formatting
  • Changes to date fields are not persisted to Polarion
Version-Specific Workaround: If you are running v24.5.0 and cannot immediately upgrade:
  1. Remove the format property from date column definitions in risksheet.json
  2. Users must enter dates manually in YYYY-MM-DD format directly into cells
  3. The calendar date picker will not function without the format property
{
  "columns": [
    {
      "id": "dueDate",
      "header": "Due Date",
      "binding": "dueDate",
      "type": "date"
      // Remove format property temporarily
    }
  ]
}
The timezone fix in version 24.5.0 introduced a regression where date columns with format property could not be saved. This was addressed as a high-priority bug. If you are still on v24.5.0, upgrade to v24.5.1 or later to restore full date column functionality with format support.
Permanent Solution: Upgrade to RISKSHEET v24.5.1 or later, which resolves the date format regression:
  1. Contact your Polarion administrator to schedule the update
  2. After upgrading, restore format properties to date columns
  3. Test date editing with calendar picker and direct cell entry
{
  "columns": [
    {
      "id": "dueDate",
      "header": "Due Date",
      "binding": "dueDate",
      "type": "date",
      "format": "yyyy-MM-dd"  // Safe to use in v24.5.1+
    }
  ]
}

​
Configuration Property Naming (readOnly)

Date columns configured with incorrect property casing will not behave as expected. The readOnly property must use camelCase, not lowercase. Incorrect (lowercase): 
{
  "columns": [
    {
      "id": "plannedEnd",
      "header": "Planned End",
      "binding": "linkedWorkItems/plannedEnd",
      "type": "date",
      "readonly": false  // WRONG: lowercase will be ignored
    }
  ]
}
Correct (camelCase): 
{
  "columns": [
    {
      "id": "plannedEnd",
      "header": "Planned End",
      "binding": "linkedWorkItems/plannedEnd",
      "type": "date",
      "readOnly": false  // CORRECT: camelCase
    }
  ]
}
All RISKSHEET configuration properties follow JavaScript camelCase convention: readOnly, showInMenu, canCreate, minWidth, etc. Using lowercase variants (readonly, showinmenu) will cause the property to be silently ignored, reverting to default behavior.

​
Date Input Methods

Nextedy RISKSHEET supports two date input methods, depending on column configuration: diagram Calendar Picker (format property defined):
  • Click cell to open visual calendar widget
  • Select date from calendar interface
  • Format property controls display format (e.g., “MM/dd/yyyy”, “dd.MM.yyyy”)
Direct Cell Entry (no format property):
  • Click cell and type date directly
  • Must use YYYY-MM-DD format (ISO 8601)
  • No calendar picker available
  • Example: 2026-03-15

​
Upstream Date Column Editing

When configuring date columns that reference upstream linked work items, ensure the binding path and readOnly property are correctly set. Example: Editable Upstream Date Column 
{
  "columns": [
    {
      "id": "reqPlannedEnd",
      "header": "Requirement Planned End",
      "binding": "linkedWorkItems/plannedEnd",
      "type": "date",
      "format": "yyyy-MM-dd",
      "readOnly": false,
      "typeProperties": {
        "role": "verifies",
        "direction": "upstream"
      }
    }
  ]
}
Key configuration points:
  • binding: Use linkedWorkItems/<fieldName> for upstream field access
  • readOnly: Must be false (camelCase) to enable editing
  • typeProperties: Defines link role and direction for upstream traceability
See Enable Editing of Upstream Columns for complete configuration examples.

​
Verify Date Column Functionality

After applying configuration fixes:
  1. Open the RISKSHEET in edit mode
  2. Click a date cell:
    • With format property: Calendar picker should appear
    • Without format property: Cell should allow direct text entry
  3. Enter or select a date
  4. Press Enter to commit the change
  5. Click 💾 Save
  6. Verify no error messages appear
  7. Refresh the page and confirm the date value persists
You should now see date columns functioning correctly with both calendar picker input (when format is defined) and direct text entry (YYYY-MM-DD format), with all changes saving successfully to Polarion.

​
See also

Support TicketsSource Code
  • CellPreviewFormatter.ts
  • GetSetUtil.java
  • ExportToExcel.ts