-
Suggestion
-
Resolution: Fixed
-
None
-
1
-
3
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Kids! They won't stay off my lawn, and now they want emoji, for crying out loud!
http://www.emoji-cheat-sheet.com/
As one user put it, "Emoji are very helpful for communicating nuance and detail, in ways that English just doesn't support. We rely heavily on emoji in our Github communication; JIRA feels...hollow without it."
The use case for us is that we'd like consistent user experience across all the products our developers use. We use Github Enterprise, so users are sad and disappointed when their cleverness can't be equally shared in JIRA.
- is related to
-
- Closed
- relates to
-
- Gathering Interest
[JRACLOUD-41592] Users Want Emoji!
Emoji can now be used in Jira Cloud. If the watchers of this issue agree, I believe this ticket can be closed, but I will wait a week before doing so in case anyone thinks it should be kept open. Thanks!
David Marshall
added a comment - Try
{{foo\(n\) + bar\(n\)}}
to inline foo(n) + bar(n), but beware that switching between Text and Visual can remove some of the backslashes. That should be a different issue, though.
David Marshall
added a comment - Try
{{foo\(n\) + bar\(n\)}}
to inline foo(n) + bar(n) , but beware that switching between Text and Visual can remove some of the backslashes. That should be a different issue, though. 
Jeff Bowlin
added a comment - Basic unicode emoji is already enabled. Even so, it is necessary to be able to prevent the emoji conversion if desired. Currently, that's not possible with any in-line text; the monospace option still resolves to basic unicode emoji:
For example, an inline monospace string like foo
+ bar
resolves to emoji. This isn't preventable and raises hackles from some of my old-school devs.
// More precisely, there's no way to inline-code this:
foo(n) + bar(y)
Confluence has an option to prevent emoji conversion, so please add that to JIRA. Alternatively, just prevent emoji for any in-line monospaced text.
Jeff Bowlin
added a comment - Basic unicode emoji is already enabled. Even so, it is necessary to be able to prevent the emoji conversion if desired. Currently, that's not possible with any in-line text; the monospace option still resolves to basic unicode emoji:
For example, an inline monospace string like foo + bar resolves to emoji . This isn't preventable and raises hackles from some of my old-school devs.
// More precisely, there's no way to inline-code this :
foo(n) + bar(y)
Confluence has an option to prevent emoji conversion, so please add that to JIRA. Alternatively, just prevent emoji for any in-line monospaced text. 
Russell Bradley
added a comment - yea... really want this too! Would totally love to do :thinkingface:
Russell Bradley
added a comment - yea... really want this too! Would totally love to do :thinkingface: At least support Unicode-standard Emoji. Here I am trying to give someone a thumbs-up in Stash.
David Wheeler
added a comment - - edited At least support Unicode-standard Emoji. Here I am trying to give someone a thumbs-up in Stash.
Eric Socolofsky
added a comment - Oh man, if only I could :thumbsup: this!
Seriously though, feature parity with Github great as much as possible. This caused problems when we imported content from Github into JIRA, and we also see a big nasty error when attempting to add emoji into any field in JIRA (though I understand this may be a config issue on our end).
And, while it may seem frivolous, it enhances the experience of using the platform and without a doubt contributes to a positive opinion of the tool in question.
Eric Socolofsky
added a comment - Oh man, if only I could :thumbsup: this!
Seriously though, feature parity with Github great as much as possible. This caused problems when we imported content from Github into JIRA, and we also see a big nasty error when attempting to add emoji into any field in JIRA (though I understand this may be a config issue on our end).
And, while it may seem frivolous, it enhances the experience of using the platform and without a doubt contributes to a positive opinion of the tool in question. 
As per this comment I am closing this ticket.
If you disagree with the closing of this ticket, please add a comment here saying why and we can reopen it as needed.