-
Suggestion
-
Resolution: Unresolved
-
2
-
4
-
Issue Summary
When trying to apply a Default value to a custom text field (Multi-line Text field) that contains an {expand} macro, it won't resolve.
On the Create Issue screen, the Text field loads the default value but the {expand} macro doesn't resolve. It simply shows as "{expand}".
It works with other macro markups (e.g. {panel}).
According to the following guide with full notation, it seems that in fact the feature has not yet been implemented: Text Formatting Notation Help
The same thing occurs if you try to add the {expand} through:
- Create/Edit Issue Action in an Automation Rule.
- Create/Edit Issue REST API endpoint.
Steps to Reproduce
1. Add a new Multi-Line Text field (or modify an existing one) and set the Default value to:
{expand: Click to Expand} Content inside the expand {expand}
3. The field must use the Wiki Style renderer.
2. Check for the field on the Issue Creation Screen. The {expand} macro is not resolved as an expand element in the field.
Expected Results
The {expand} macro resolves in the screen
Actual Results
The {expand} macro does not resolve.
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
- mentioned in
-
Page Loading...