Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Description field formatting


I'd love to see some type of formatting in the description field of a field in Jira Product Discovery. For example, we use it for I.C.E. and use the description to help standardize things like effort and value.

The first image below is how it's entered while editing and closer to what we'd like to see (it's more readable).



The second image is what's displayed to users once it's saved if you scroll over the field.



I agree with that.

Should not be a big problem, changing it from a text field to an editor field.

Like # people like this

Thanks @Jimi Wikman , just let us know when the pull request is ready 😉

Yep, good point @brent_johnson - let us see what we can do there!

Like # people like this

@Tanguy CrussonJust need access to the repo and the component libraries ;)

Jokes aside, if you can make that change, that would be great. No, make that awesome :)

@Jimi Wikman 😂

We've put it on the short list. Just to give you some insider info on this as to why things like this aren't always easy:

  • We checked and this description it's not a Jira Product Discovery specific thing - it is something that's used across Jira, and it's not a rich text field. 
  • Changing something for the whole of Jira (Jira Software, Jira Service Management, Jira Work Management, etc.) isn't trivial - in particular there are a number of screens this field may surface across the product and admin experience. And many teams involved owning these things. 
  • However, in this case we found a way to limit the impact to Jira Product Discovery only. The solution's a bit hacky and will cause us a bit of grief later down the line
  • We discussed this in the team and decided that, yes, it's worth it. The reason for that is that we want product teams to use Jira Product Discovery to share their plans with everyone (we're deep in that topic at the moment) - and a limitation like this one doesn't help with that.
  • Also, we received requests from people wanting to document fields in documents (a Confluence page, a Google Doc) - e.g. to explain "these are the product areas and what they mean" in greater length. From a rich text field, that becomes easy

So, the short answer is: changes like this are not always as trivial as they may seem - but in that case we'll do it because it helps with the mission of the product. There are cases where we won't do things y'all ask that seem easy, more often than not it's because they're not !

Like Jimi Wikman likes this

First of all, I hear you. I know all too well the pain of needing to change global components or trying to motivate breaking up an existing architecture that is restricting progress when time and money are limited. That just make me appreciate the effort you made all the more.

Secondly I really appreciate you taking the time to explain the challenges as that is an excellent way to ensure we understand why things may or may not appear as quickly as we might think.

I think this was one of the best replies I have seen in a long time to feature requests like these.

Whatever they are paying you @Tanguy Crusson it is not enough :) Keep up the awesome work and have a great day!

Like Tanguy Crusson likes this

hahaha thanks @Jimi Wikman , your reply made my day

Like Jimi Wikman likes this

I have also run into this desire / need regularly.... not just for easier reading, but I would like to add a "Learn More" link that takes users to Confluence pages that provide more training and context on the field + standard usage + model + potential training resources. 

Like Tanguy Crusson likes this

Cool, thanks for the context @J P - it sounds like what we have planned would help you there


Log in or Sign up to comment

Atlassian Community Events