I like the new info panels in the new Jira issue view!
We have some automation that creates the old-style panels with the wiki markup, but their styling is broken now in the new view.
Is there a way to create an info panel via the new-style markdown (as opposed to via the WYSIWYG editor)?
EDIT: Turns out you can create the new-style panels via the API by using the old-style `{panel}` syntax and choosing the correct `bgColor`. Here are the current colors (sorry, this textbox ate my code formatting):
const InfoPanelColor: { [K in InfoPanelStyle]: string } = { [InfoPanelStyle.Error]: '#ffebe6', [InfoPanelStyle.Info]: '#e3fcef', [InfoPanelStyle.Success]: '#e3fcef', [InfoPanelStyle.Warning]: '#fffae6', }
So, I'll change this request to: If you break that functionality ^, please provide a substitute. Thanks!
As @Harvey Rogers has mentioned in his update - the old panel syntax works and here are examples for the existing panel types:
{panel:bgColor=#ffebe6}
This error panel
{panel}
{panel:bgColor=#deebff}
This info panel
{panel}
{panel:bgColor=#e3fcef}
This success panel
{panel}
{panel:bgColor=#fefae6}
This warning panel
{panel}
{panel:bgColor=#eae6ff}
This note panel
{panel}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nope, that old formatting is not working anymore in new cloud experience. Now there is an Info Panel.
The problem is that I can't copy the formatting layout from one task and paste it to another issue description; as it was possible in old view.
Have you found out the better way of doing it?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The code/markdown does not work when write it down manually into the issue, but it works when an automation action writes it to the issue description. This is what this topic is about.
Regarding the copy-paste - it works when you copy-paste already formatted text (no markdown) form issue to issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank, it's work fine!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@KoCMoHaBTa this was working fine, now there seems to have been some update and it's borked.
Does anyone know the new formatting for: info, error, success, and warning panel?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @KoCMoHaBTa, I just happen to see your reply about formating panels within jira fields as the default value.
I am using those wiki markups to display an info panel within a "Message Custom Field"
Using {panel:bgColor=#deebff} does display a blue background panel but not the "(i)" icon.
I do not find the documentation about parameters that can be passed to the {panel}. I guess there would be some "icon=info" option or something similar. Do you have any clue about that?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry, no clue. Unfortunately I can't experiment, because I'm no longer managing the JIRA for my organization and don't have access to these anymore.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
FWIW the above solution still works.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Torsten Walter , please provide the markup syntax used.
The idea is to get this auto-populated.
The panels do work when editing the description, what is NOT working is the auto-creation of those panels.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I used the exact code provided above with JiraIntegration+ from a Slack workflow.
Here's how it looks now after we modified for our use case.
It works two multiple ways:
- markup is directly added to database, skipping the editor
- formatted content is copied from another ticket or from a confluence page
What doesn't work is copying the markup and pasting it into the editor.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Text formatting notation help here: https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Harvey,
Thank you for reaching out to Atlassian Community!
I've searched on our documentation and also on the markdown guide, but there is no markdown for info, warning, note, so, for now, it's possible to add only using the WYSIWYG editor.
We still don't have a feature request for that, so please, feel free to raise one on jira.atlassian.com (project JRACLOUD) adding more details and information about why this feature is important for your environment.
Regards,
Angélica
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Scott,
Currently, Server supports only Wiki Markup. We have a feature request suggesting Markdown for Server:
Please, click on vote and watch to receive updates about the feature.
Regards,
Angélica
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please stop dumbing down Jira. Keyboard functionality keeps getting dropped making Jira harder to use.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Harvey,
Default texts are added using the Wiki-Style renderer, and Wiki markup is used for this in Field configuration. In contrast, the issue view uses ADF, where markdown and keyboard shortcuts are used. Please refer to the article below for more details on this.
How is Field Configuration's wiki-style mark-up converted to Rich text in Jira Service Management
Regards,
Haripriya
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.