-
Sub-task
-
Resolution: Won't Fix
-
High
-
None
-
None
Hi everyone,
Thank you for your patience while we investigate this issue.
Our investigation discovered a high degree of complexity to enable rich text support for single line custom fields. The team with the expertise required to do this work, is currently working on a range of performance improvements. Since the usage of single line text fields is low, weâve decided to prioritise performance improvements (which impacts more people). As a result, we have decided not to support rich text (either wiki markup or markdown) in single line custom fields in the new issue view. We do however have other custom fields that offer rich text (more details below). We will make some minor changes to make this clear in the product.
What we will be changing
We will rollout the following changes over the next week:
- âText Field (Single Line)â will be renamed to âShort text (plain text only)â
- âText Field (Multi-Line)â will be renamed to âParagraph (supports rich text)â
- We will also introduce text wrapping for single line custom fields (currently, text will truncate when a character limit is reached)
Other custom fields available
There are two other custom fields we recommend using if rich text is required in the new issue view:
- âURL Fieldâ - if all you need is to display a web URL as a hyperlink.
- âParagraphâ (formerly Text Field (multi line)) - if you want more rich text functionality, including links to URLs, styling text with bold, colour and/or italics, or anything else available in the Atlassian editor.
The above fields can also be used for automations and ecosystem apps and will support rich text available through markdown.
We acknowledge that the above changes will require some of you to spend time and effort re-configuring your project/s and we do apologise for this inconvenience caused.
As this issue refers specifically to the support of wiki markup, we will be closing this ticket. The decision was made a number of years ago to replace wiki markup with full markdown support. You can refer to our public comms on this here
Thanks
The Atlassian Cloud team
Summary
When creating a custom field, regardless of what is configured it uses the Default Text Renderer in Bento.
Steps to Reproduce
- Create a single line custom field
- Set the renderer to Wiki Style and add the field to a Screen
Expected Results
The formatting is rendered
Actual Results
The format is not rendered and the contents of the field are displayed in the Default text
Workaround
- is duplicated by
-
-
- Closed
-
-
JRACLOUD-69984 Custom fields formatting is not converted to markdown in the new Jira issue view
-
- Closed
-
- is related to
-
-
- Closed
-
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
-
-
-
-
[JRACLOUD-69877] Wiki Style Renderer does not work for custom Single Line Text fields
Hey, did I understand correctly that wiki style renderer doesn't work for Single line text field but it still presents as an option there?
Is there another Atlassian ticket to remove this not working functionality from single line text fields in field configuration? đ
| Remote Link | Original: This issue links to "Page (Confluence)" [ 575034 ] |
Fair enough that you are not going to implement Wiki formatting for a single line field, but can you at least remove the Field Configuration option that allows you to change it to Wiki Markup. That would be a small change and would avoid confusion.
Hi 5e22f3c7b1cb, would you be able to contact our support team so we can look into this properly for you? thank you
I've enabled the wiki field renderer for a custom paragraph field and am still unable to see the new renderer.
Field configuration:
Issue screen:
Hi,
Yes it was the wiki renderer was not activated, Thank's.
All that's left is to change all fields and script to use that 
Regards,
RĂ©mi de Chalendar
Hi 617c7a68cfc7 - if you switch to the old issue view (using the three dot menu and then selecting see the old view), does the text render in bold and colour? If not, can you double check that the wiki renderer has been selected? https://support.atlassian.com/jira-cloud-administration/docs/specify-field-behavior/
| Description |
Original:
{panel:title=Atlassian Update - 2 September 2021|borderStyle=solid|borderColor=#2684ff|titleBGColor=#2684ff|bgColor=#ffffff}
Hi everyone, Thank you for your patience while we investigate this issue. Our investigation discovered a high degree of complexity to enable rich text support for single line custom fields. The team with the expertise required to do this work, is currently working on a range of performance improvements. Since the usage of single line text fields is low, weâve decided to prioritise performance improvements (which impacts more people). As a result, we have decided not to support rich text (either wiki markup or markdown) in single line custom fields in the new issue view. We do however have other custom fields that offer rich text (more details below). We will make some minor changes to make this clear in the product. *What we will be changing* We will rollout the following changes over the next week: * âText Field (Single Line)â will be renamed to âShort text (plain text only)â * âText Field (Multi-Line)â will be renamed to âParagraph (supports rich text)â * We will also introduce text wrapping for single line custom fields (currently, text will truncate when a character limit is reached) *Other custom fields available* There are two other custom fields we recommend using if rich text is required in the new issue view: * âURL Fieldâ - if all you need is to display a web URL as a hyperlink. * âParagraphâ (formerly Text Field (multi line)) - if you want more rich text functionality, including links to URLs, styling text with bold, colour and/or italics, or anything else available in the Atlassian editor. The above fields can also be used for automations and ecosystem apps and will support rich text available through markdown. Ream more on markdown [here|[https://support.atlassian.com/jira-software-cloud/docs/markdown-and-keyboard-shortcuts/]] We acknowledge that the above changes will require some of you to spend time and effort re-configuring your project/s and we do apologise for this inconvenience caused. As this issue refers specifically to the support of wiki markup, we will be closing this ticket. The decision was made a number of years ago to replace wiki markup with full markdown support. You can refer to our public comms on this [here|https://community.developer.atlassian.com/t/jira-cloud-new-issue-view-editor-changes/29993] Thanks The Atlassian Cloud team {panel} h3. Summary When creating a custom field, regardless of what is configured it uses the Default Text Renderer in Bento. h3. Steps to Reproduce # Create a single line custom field # Set the renderer to Wiki Style and add the field to a Screen h3. Expected Results The formatting is rendered h3. Actual Results The format is not rendered and the contents of the field are displayed in the Default text h3. Workaround |
New:
{panel:title=Atlassian Update - 2 September 2021|borderStyle=solid|borderColor=#2684ff|titleBGColor=#2684ff|bgColor=#ffffff}
Hi everyone, Thank you for your patience while we investigate this issue. Our investigation discovered a high degree of complexity to enable rich text support for single line custom fields. The team with the expertise required to do this work, is currently working on a range of performance improvements. Since the usage of single line text fields is low, weâve decided to prioritise performance improvements (which impacts more people). As a result, we have decided not to support rich text (either wiki markup or markdown) in single line custom fields in the new issue view. We do however have other custom fields that offer rich text (more details below). We will make some minor changes to make this clear in the product. *What we will be changing* We will rollout the following changes over the next week: * âText Field (Single Line)â will be renamed to âShort text (plain text only)â * âText Field (Multi-Line)â will be renamed to âParagraph (supports rich text)â * We will also introduce text wrapping for single line custom fields (currently, text will truncate when a character limit is reached) *Other custom fields available* There are two other custom fields we recommend using if rich text is required in the new issue view: * âURL Fieldâ - if all you need is to display a web URL as a hyperlink. * âParagraphâ (formerly Text Field (multi line)) - if you want more rich text functionality, including links to URLs, styling text with bold, colour and/or italics, or anything else available in the Atlassian editor. The above fields can also be used for automations and ecosystem apps and will support rich text available through markdown. We acknowledge that the above changes will require some of you to spend time and effort re-configuring your project/s and we do apologise for this inconvenience caused. As this issue refers specifically to the support of wiki markup, we will be closing this ticket. The decision was made a number of years ago to replace wiki markup with full markdown support. You can refer to our public comms on this [here|https://community.developer.atlassian.com/t/jira-cloud-new-issue-view-editor-changes/29993] Thanks The Atlassian Cloud team {panel} h3. Summary When creating a custom field, regardless of what is configured it uses the Default Text Renderer in Bento. h3. Steps to Reproduce # Create a single line custom field # Set the renderer to Wiki Style and add the field to a Screen h3. Expected Results The formatting is rendered h3. Actual Results The format is not rendered and the contents of the field are displayed in the Default text h3. Workaround |
| Description |
Original:
{panel:title=Atlassian Update - 2 September 2021|borderStyle=solid|borderColor=#2684ff|titleBGColor=#2684ff|bgColor=#ffffff}
Hi everyone, Thank you for your patience while we investigate this issue. Our investigation discovered a high degree of complexity to enable rich text support for single line custom fields. The team with the expertise required to do this work, is currently working on a range of performance improvements. Since the usage of single line text fields is low, weâve decided to prioritise performance improvements (which impacts more people). As a result, we have decided not to support rich text (either wiki markup or markdown) in single line custom fields in the new issue view. We do however have other custom fields that offer rich text (more details below). We will make some minor changes to make this clear in the product. *What we will be changing* We will rollout the following changes over the next week: * âText Field (Single Line)â will be renamed to âShort text (plain text only)â * âText Field (Multi-Line)â will be renamed to âParagraph (supports rich text)â * We will also introduce text wrapping for single line custom fields (currently, text will truncate when a character limit is reached) *Other custom fields available* There are two other custom fields we recommend using if rich text is required in the new issue view: * âURL Fieldâ - if all you need is to display a web URL as a hyperlink. * âParagraphâ (formerly Text Field (multi line)) - if you want more rich text functionality, including links to URLs, styling text with bold, colour and/or italics, or anything else available in the Atlassian editor. The above fields can also be used for automations and ecosystem apps and will support rich text available through markdown - read more on markdown [here|[https://support.atlassian.com/jira-software-cloud/docs/markdown-and-keyboard-shortcuts/]] We acknowledge that the above changes will require some of you to spend time and effort re-configuring your project/s and we do apologise for this inconvenience caused. As this issue refers specifically to the support of wiki markup, we will be closing this ticket. The decision was made a number of years ago to replace wiki markup with full markdown support. You can refer to our public comms on this [here|https://community.developer.atlassian.com/t/jira-cloud-new-issue-view-editor-changes/29993] Thanks The Atlassian Cloud team {panel} h3. Summary When creating a custom field, regardless of what is configured it uses the Default Text Renderer in Bento. h3. Steps to Reproduce # Create a single line custom field # Set the renderer to Wiki Style and add the field to a Screen h3. Expected Results The formatting is rendered h3. Actual Results The format is not rendered and the contents of the field are displayed in the Default text h3. Workaround |
New:
{panel:title=Atlassian Update - 2 September 2021|borderStyle=solid|borderColor=#2684ff|titleBGColor=#2684ff|bgColor=#ffffff}
Hi everyone, Thank you for your patience while we investigate this issue. Our investigation discovered a high degree of complexity to enable rich text support for single line custom fields. The team with the expertise required to do this work, is currently working on a range of performance improvements. Since the usage of single line text fields is low, weâve decided to prioritise performance improvements (which impacts more people). As a result, we have decided not to support rich text (either wiki markup or markdown) in single line custom fields in the new issue view. We do however have other custom fields that offer rich text (more details below). We will make some minor changes to make this clear in the product. *What we will be changing* We will rollout the following changes over the next week: * âText Field (Single Line)â will be renamed to âShort text (plain text only)â * âText Field (Multi-Line)â will be renamed to âParagraph (supports rich text)â * We will also introduce text wrapping for single line custom fields (currently, text will truncate when a character limit is reached) *Other custom fields available* There are two other custom fields we recommend using if rich text is required in the new issue view: * âURL Fieldâ - if all you need is to display a web URL as a hyperlink. * âParagraphâ (formerly Text Field (multi line)) - if you want more rich text functionality, including links to URLs, styling text with bold, colour and/or italics, or anything else available in the Atlassian editor. The above fields can also be used for automations and ecosystem apps and will support rich text available through markdown. Ream more on markdown [here|[https://support.atlassian.com/jira-software-cloud/docs/markdown-and-keyboard-shortcuts/]] We acknowledge that the above changes will require some of you to spend time and effort re-configuring your project/s and we do apologise for this inconvenience caused. As this issue refers specifically to the support of wiki markup, we will be closing this ticket. The decision was made a number of years ago to replace wiki markup with full markdown support. You can refer to our public comms on this [here|https://community.developer.atlassian.com/t/jira-cloud-new-issue-view-editor-changes/29993] Thanks The Atlassian Cloud team {panel} h3. Summary When creating a custom field, regardless of what is configured it uses the Default Text Renderer in Bento. h3. Steps to Reproduce # Create a single line custom field # Set the renderer to Wiki Style and add the field to a Screen h3. Expected Results The formatting is rendered h3. Actual Results The format is not rendered and the contents of the field are displayed in the Default text h3. Workaround |
Dear support I have the same issue than @Slava Gefen.
Thank you