Paste in emoji's in the new JIRA issue view

Question

In the old JIRA issue view I could paste in something like the following:

(/) Did the Pipelines build pass?
(/) Did code coverage pass?
(/) When tested manually did everything work?
(x) Were tests added to cover any new code?
(x) Were tests updated to no longer use deprecated methods?
(/) Have queries been optimized for low query counts (i.e. select_related, prefect_related)?
(/) Was a "To Test" section added to the issue description, explaining what views were affected?
(/) Were relevant exports updated?

and everywhere I had (/) and (x) it would get turned into emojis after it was saved. Is there a way to have this same type of functionality in the new view. If not, can that functionality be added? Because without the functionality, it takes more time to make comments with my pre-defined checklists.

Brent O_Connor · Answer

@Paweł Albecki

Yeah, that didn't work.

https://monosnap.com/file/z4TcH4t0zephiNxwFyUGNn2yMciwqS

Paweł Albecki · Answer

You don't need a custom checklist app. Try this:

https://pastebin.com/4CWQQGzu (Apologies but I couldn't paste it here)

Best,

Paweł

Daniel Eads · Answer

Hey Brent,

The new issue view also uses our new editor which is markdown compliant. The functionality of converting things like (x) and (/) to emoji was part of the wiki markup renderer in the old editor.

The good news is the new editor is fully emoji-compliant 🎉for bringing in your standard ✅and ❌unicode emoji. But that does come at a cost of needing to have those available either from your keyboard or copy/pasting them from somewhere.

I feel for you as I also have relied heavily on wiki-rendered checklists and tables for making the details and progress on issues very clear. It's an adjustment. Maybe check out the checklist apps on Marketplace as well - one called Issue Checklist Free (there's a paid version of this also) lets you save commonly-used checklists as templates so you can bring in all the questions you want to work through without any fiddling. It seems like that might be a great fit for the type of list in your example.

Cheers,
Daniel