Say more with rich text

[#1]

Hey folks! My name is Andrew and I’m a PM on the Jira Align team. I have two exciting updates to share:

1. We’ve added the Atlassian editor to feature descriptions. Take advantage of advanced formatting capabilities like tables, code blocks, info panels, and more.

2. Rich text now syncs between Jira and Jira Align for feature descriptions. Formatting that you enter in one tool will show up seamlessly in the other tool. Go ahead and make edits, like adding a table column or bolding a word. All those changes will sync back-and-forth between tools, so that all your stakeholders can stay on the same page.

Before

After

With version 11.5.X, we’ve resolved one of Jira Align’s biggest pain points. It’s been one of our oldest and most highly upvoted JAC suggestions. This change will go into effect automatically for Jira Align instances connected to Jira Cloud or Jira Data Center.

You’ll no longer have to pivot back and forth from Jira Align to Jira, trying to decipher the context of a piece of work. Get all the information you need, wherever you need it. Use the new Atlassian editor to capture all of the nuance, complexity, and structure of the projects you’re delivering, so that nothing gets lost in translation.

Does this editing experience feel familiar? That’s because it’s the same editor you know and love from our other Atlassian products, like Jira Cloud and Confluence Cloud. We’re bringing Jira Align one step closer to the Atlassian platform.

Note that not all formatting types will render the same in Jira Align. Smartlinks, images and other attachments, user mentions, emojis, status lozenges, expands, and dates will have a different appearance in Jira Align.

For more information about how administrators can change this setting, check out our release notes and our help documentation!

Feedback

We'd love to hear from you! Let us know what you think of these new capabilities and where else in the product you’d like to have the Atlassian Editor.

[John Buchenberger]

Hi Andrew, 

Thanks for the announcement.  I know that the community has been anticipating this improvement.  I'm curious about why it's limited to features and when it might be available on all work items with descriptions? 

Thanks!

[John Buchenberger]

Just to answer the question you posed directly, we were hoping that all description fields would have been upgraded with the new functionality.  If I were to prioritize, Capabilities would be the most important work item where the editor would help us.  

[Bhanu Prakash]

@Andrew Zhang , From the Screen-print is there an option of Bullet list in the description. 
But i do not see that there is a numbering list along with Bullet List. 

Is this some thing that will be  enabled by default or do we get only Bullet List for now while creating from Jira  Align ? 

[Isaac Greenberg]

This is great, but comments not syncing between Jira and Align will still cause pivoting between the tools for important context clues. https://jira.atlassian.com/browse/JIRAALIGN-5516

[Andrew Zhang]

@Bhanu Prakash, you should get both bulleted list and numbered list in Jira Align, enabled by default.

[Andrew Zhang]

@John Buchenberger Good feedback, we plan to work on additional work items in the future. Features are just the beginning. We would likely do Portfolio Epics, then Capabilities

[Jayanthi Rayapalya Vijendra]

@Andrew Zhang - Hi Andrew, On testing we found that the Rich text in the description field renders correctly in Jira Align only if Jira uses the JEditor Renderer. If the WikiStyle renderer is used for the Description field in Jira, we don't see the Rich text sync over to JA. 

[Andrew Zhang]

@Jayanthi Rayapalya Vijendra can you file a ticket with support so we can assist?