Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-82347

Field Description and Field Configuration Description don't support emojis

      Issue Summary

      Adding emojis to the field description does not render all available emojis. 

      Steps to Reproduce

      1. Go to Custom Fields > Add a description like the following one:
        1. Screen Recording 2023-11-13 at 18.49.04.mov

      You can see the same behavior for Field Configuration, which is much more confusing since it displays the emoji when you are done editing:

      Expected Results

      I will see those emojis in my field description. 

      Actual Results

      Jira will convert it to text, but won't show them as emojis. 

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available.

            [JRACLOUD-82347] Field Description and Field Configuration Description don't support emojis

            Dom added a comment - - edited

            According to your Bug Policy (emphasis mine)

            Priority 2 - High

            A feature is unavailable, application performance is significantly degraded, or users job functions are impaired.

            • the application performs slowly and fails intermittently
            • application is functional, but frequently used gadgets or macros don't work
            • specific editing features fail

            There are no workarounds for this feature, it has a direct user impact, and the addition of these icons greatly assists in breaking up the wall of text and highlighting different elements of the description when used as guidance and training for value entry. Our overall approach in server (this is related to our migration) used the lightbulbs to show where automations were impacting the field, and different stars to call out business requirements in different contexts. This causes all of my icons in the server example to fail and creates a ton of formatting issues for the user as a result everywhere a description is used.

             

            I'm not talking about all the icons, to be clear. These codes only - Green highlighted ones work currently, Yellow doesn't work but changes correctly, Red highlight is where info is also missing the ":" 

            Raw code in my Field Configuration Description test

             

            Preview in Field Configurations

             

            Broken Parsed Issue View display

            Dom added a comment - - edited According to your Bug Policy (emphasis mine) Priority 2 - High A feature is unavailable , application performance is significantly degraded, or users job functions are impaired. the application performs slowly and fails intermittently application is functional, but frequently used gadgets or macros don't work specific editing features fail There are no workarounds for this feature, it has a direct user impact, and the addition of these icons greatly assists in breaking up the wall of text and highlighting different elements of the description when used as guidance and training for value entry. Our overall approach in server (this is related to our migration) used the lightbulbs to show where automations were impacting the field, and different stars to call out business requirements in different contexts. This causes all of my icons in the server example to fail and creates a ton of formatting issues for the user as a result everywhere a description is used.   I'm not talking about all the icons, to be clear. These codes only - Green highlighted ones work currently, Yellow doesn't work but changes correctly, Red highlight is where info is  also missing the ":"   Raw code in my Field Configuration Description test   Preview in Field Configurations   Broken Parsed Issue View display

            Dom added a comment -

            Hey all,

            We use descriptions for a number of features in Server / DC, which we are actively trying to migrate into Cloud with.

            Since Jira has a lot of integrated "Create Issue" functionality that cannot support Required fields beyond Summary, we've gotten used to using Conditions / Validations to provide those protections where they are needed.

            However, the Description becomes VERY important in clearly showing exactly what is and isn't necessary for each project and its associated issues / fields.

            The editor for the Field Configurations / Contexts is using wiki-markup, and shows a preview with the old editor.

            The new editor experience is in the user-facing issue screens... which parse only some of the characters currently.

            It's clear that it's intent is to support the wiki-markup icons, but 2/3 are transformed in text (from being wrapped in parenthesis to display the equivalent new words wrapped colons) but not rendered into the equivalent icons in the new view. Info actually is missing the second "closing" colon as well.

            Not having these render means that all of my Descriptions for migration will require cleanup and substantial formatting changes, at minimum.

            Most importantly, the icons help call attention to multiple critical details - lightbulbs () were used for expected automations / post actions, for instance. Lacking these morphs the descriptions into a block wall of text that's painful to parse visually. It's FAR harder and more confusing to be confronted with blocks of text in a create / edit screen without these icons calling attention to different details and context-relevant notes, breaking up experiences.

            I'm hoping that it's a simple parsing fix for the remainder of the icons and adding the : for :info:  

            Thanks!

            Dom added a comment - Hey all, We use descriptions for a number of features in Server / DC, which we are actively trying to migrate into Cloud with. Since Jira has a lot of integrated "Create Issue" functionality that cannot support Required fields beyond Summary, we've gotten used to using Conditions / Validations to provide those protections where they are needed. However, the Description becomes VERY important in clearly showing exactly what is and isn't necessary for each project and its associated issues / fields. The editor for the Field Configurations / Contexts is using wiki-markup, and shows a preview with the old editor. The  new editor experience is in the user-facing issue screens... which parse only some of the characters currently. It's clear that it's intent is to support the wiki-markup icons, but 2/3 are transformed in text (from being wrapped in parenthesis to display the equivalent new words wrapped colons) but not rendered into the equivalent icons in the new view. Info actually is missing the second "closing" colon as well. Not having these render means that all of my Descriptions for migration will require cleanup and substantial formatting changes, at minimum. Most importantly, the icons help call attention to multiple critical details - lightbulbs ( ) were used for expected automations / post actions, for instance. Lacking these morphs the descriptions into a block wall of text that's painful to parse visually. It's FAR harder and more confusing to be confronted with blocks of text in a create / edit screen without these icons calling attention to different details and context-relevant notes, breaking up experiences. I'm hoping that it's a simple parsing fix for the remainder of the icons and adding the : for :info:   Thanks!

              2aca7cfc99f9 Sayani Ghosh
              ba93886ee67a Luísa
              Affected customers:
              1 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: