-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
Component/s: Whiteboard
-
None
-
1
-
Severity 3 - Minor
-
Warranty
Problem
When creating a Jira Story from a Confluence whiteboard, the operation fails if the issue type includes a "Message Field" custom field. This occurs even though the "Message Field" is not required and is intended only for user guidance. The error "Operation value must be a string" is returned, preventing issue creation.
Environment
- Confluence Cloud (Whiteboards)
- Jira Cloud (Story issue type with "Message Field" custom field, not required)
Steps to Reproduce
- Open a Confluence whiteboard.
- Add a sticky note.
- Select "Convert to Jira issue".
- Choose a Jira project and select the Story issue type that includes the "Message Field" (not required).
- Attempt to create the issue.
Expected Results
The Jira Story should be created successfully, with the non-required "Message Field" ignored during creation.
Actual Results
The creation fails with the following error:
Operation value must be a string
The issue is not created. This only occurs when creating from a Confluence whiteboard; creating the same Issue or Story directly in Jira works as expected.
Workaround
- Create the Jira Story directly in Jira, bypassing the whiteboard integration.
- Alternatively, consider using a different custom field type (e.g., "Text field (multi-line)") if possible.
Notes
- The "Message Field" is not required in the workflow or field configuration and is intended for display/guidance only.
- The problem occurs even when the "Message Field" is not required.
- Similar to CONFCLOUD-78496, but this affects non-required fields as well.
- is related to
-
CONFCLOUD-78496 Whiteboard does not support required "Message Custom Field" on Jira Issue creation despite displaying field
-
- Short Term Backlog
-
-
CONFCLOUD-78498 Possibility to be able to create a Jira Issue on Confluence in case it have unsupported Custom fields
- Gathering Interest
- mentioned in
-
Page Loading...