Query Parsing Errors

​

Identify the Query Error Source

​

Step 1: Locate the Error Message

​

Check Browser Console

1. Open RISKSHEET in your browser
2. Press F12 to open Developer Tools
3. Navigate to the Console tab
4. Look for error messages containing “Unparseable query” or “ParseException”
5. Note the query fragment shown in the error

​

Check Polarion Server Logs

1. Access Polarion server logs (typically /opt/polarion/data/logs/)
2. Search for “Unparseable query” or “ParseException”
3. Identify the malformed query and the triggering operation
4. Note if the error mentions auto-assignment, custom fields, or workflow actions

• Unparseable query error? — Check error location
  • RISKSHEET config? — Step 2: Fix RISKSHEET queries
  • Auto-assignment rule? — Step 3: Fix auto-assignment
  • Column configuration? — Step 4: Fix column queries
  • Unknown source? — Step 5: Validate all queries

​

Step 2: Fix RISKSHEET Query Configuration

​

Common Query Syntax Errors

// ❌ WRONG - will fail if document name has spaces
"query": "type:risk AND module.id:Safety Requirements"

// ✅ CORRECT - quotes handle spaces
"query": "type:risk AND module.id:\"Safety Requirements\""

// ❌ WRONG - lowercase operators not supported
"query": "type:risk and status:open"

// ✅ CORRECT - uppercase boolean operators
"query": "type:risk AND status:open"

// ❌ WRONG - missing colon between field and value
"query": "type risk"

// ✅ CORRECT - proper field:value syntax
"query": "type:risk"

// ❌ WRONG - parentheses need escaping
"query": "title:Risk (High)"

// ✅ CORRECT - escape special characters
"query": "title:\"Risk (High)\""

​

Validate Query Syntax

1. Open Polarion’s Advanced Search page
2. Switch to Lucene Query mode
3. Paste your query and execute
4. If errors appear, correct the syntax
5. Once working, copy the validated query to RISKSHEET configuration

​

Step 3: Fix Auto-Assignment Configuration Issues

​

Identify Problematic Auto-Assignment Rules

1. Navigate to Administration → Workflow and Fields → Auto-Assignment Rules
2. Review rules applied to work item types used in your RISKSHEET
3. Look for template expressions like {{variable}} in assignment logic
4. Check if these expressions are properly evaluated before use in queries

​

Common Auto-Assignment Query Issues

## ❌ WRONG - template not evaluated, creates literal "{{7*7}}" in query
assignee:{{7*7}}

## ✅ CORRECT - template evaluated to value before query construction
#set($calculatedValue = 49)
assignee:user_${calculatedValue}

## ❌ WRONG - if $workItem.customField is null or contains special chars
project.id:$workItem.customField.projectId

## ✅ CORRECT - verify value exists and escape special characters
#if($workItem.customField.projectId)
project.id:"$workItem.customField.projectId"
#end

​

Disable Problematic Rules Temporarily

1. Navigate to the rule in Administration
2. Set the rule to Inactive
3. Test if documents load correctly
4. Fix the rule logic before re-enabling

​

Step 4: Fix Column Query Configuration

​

Review Column typeProperties

1. Open RISKSHEET Configuration Editor
2. Locate columns with typeProperties.query
3. Validate each query using Polarion’s Advanced Search
4. Fix syntax errors using patterns from Step 2

{
  "id": "linkedReqs",
  "type": "itemLink",
  "typeProperties": {
    "query": "type:requirement AND project.id:PROJ",  // ✅ Valid
    "types": "requirement"
  }
}

{
  "id": "linkedReqs",
  "type": "itemLink",
  "typeProperties": {
    "query": "type requirement project PROJ",  // ❌ Missing colons and AND
    "types": "requirement"
  }
}

​

Test Column Queries Independently

1. Copy the typeProperties.query value
2. Test in Polarion Advanced Search → Lucene Query
3. Add project and document context if needed:
   Copy

   Ask AI

   type:requirement AND project.id:MYPROJECT AND module.id:"Document Name"
   
4. Verify the query returns expected work items
5. Update RISKSHEET configuration with corrected query

​

Step 5: Validate All Query Configurations

​

Configuration Properties to Review

​

Validation Checklist

• Boolean operators are uppercase (AND, OR, NOT)
• Field names use correct syntax: field:value or field.subfield:value
• Multi-word values are quoted: module.id:"Document Name"
• Special characters are escaped or quoted
• Template expressions (if any) are properly evaluated
• Query executes without errors in Polarion Advanced Search

​

Step 6: Check System Field Restrictions

​

Protected System Fields

• id (work item ID)
• status (workflow status)
• type (work item type)
• project (project ID)
• outlineNumber (document hierarchy position)

​

Common Query Patterns

​

Filter by Work Item Type

type:risk
type:(risk hazard)

​

Filter by Project and Document

project.id:MYPROJECT AND module.id:"Safety Analysis"

​

Filter by Date Range

created:[NOW-90DAYS TO NOW]
updated:[2024-01-01 TO 2024-12-31]

​

Filter by Custom Enum Field

customField.priority:high
customField.status:(open inProgress)

​

Filter by User Assignment

assignee:john.doe
assignee:(john.doe jane.smith)

​

Combine Multiple Conditions

type:risk AND status:(open inProgress) AND customField.severity:critical

​

Verification

• RISKSHEET loads without query parsing errors
• Polarion logs show no “Unparseable query” messages
• All queries execute successfully in Polarion Advanced Search
• Columns displaying linked items load data correctly
• Auto-assignment rules execute without errors

​

See Also

• Reference: Query Syntax - Complete Lucene query syntax reference
• Configure Queries - Advanced query configuration guide
• Slow Page Loading - Optimize query performance
• Reference: Polarion Version Compatibility - Plugin version requirements