Jira plugin that switches rich formatting on/off on the fly

It would be useful to have a checkbox (or similar control)

[x] allow rich formatting

below description/comments. Has anybody heard of such a plugin?

Thanks.

3 answers

1 vote
Steven Behnke Community Champion Aug 08, 2014

I don't see a way that you could toggle this functionality off and on without getting really gritty with the jira development.


It may just be better to try a different rich text option: https://marketplace.atlassian.com/plugins/com.jiraeditor.jeditor

0 votes

No, there isn't one - you eithrer use wiki markup or you don't. If you enable it, then to use plain text, don't enter any wiki markup!

Thanks, Nic. But unfortunatelly this is not suitable for a scenario I have. Some of our users don't want to use wiki markup. And they don't want their data to interpreted as a markup'ed data. They also find unacceptable to enclose their text in a {noformat} tag. We don't want to put them in a separate project or give them a separate set of issues (with the only difference that they come with a simple renderer rather than rich text one) -- that will only confuse people and make the whole system less comfortable to use. So we need something more flexible in this case.

I don't see how adding an arbitrary and confusing flag to every text field makes it more simple. The way to simplify the is for a subset of your users is to tell them to use plain English and not try to do any of the cclever formatting that they already say that they don't want to do. Plain writing means no markup, and hence no formatting. It can't get "more flexible" than "don't write formatted stuff if you don't need it"

Nic, I feel a bit of negativity. There's no need to. I should've mentioned this before, but it slipped my mind. Sorry, my fault. One thing that makes this use case special, is that there are ennormous amount of issues already in the tracker. Some of them use characters and combinations of characters which will be regarded as markdown should we turn the rich editing on. We want to avoid that.

Yes, I see that, it was quite negative. My point was that it would add complexity and inconsistency, for no real gain. For your case, I'd simply leave it disabled.

Thanks, Nic. But unfortunatelly this is not suitable for a scenario I have. Some of our users don't want to use wiki markup. And they don't want their data to interpreted as a markup'ed data. They also find unacceptable to enclose their text in a {noformat} tag. We don't want to put them in a separate project or give them a separate set of issues (with the only difference that they come with a simple renderer rather than rich text one) -- that will only confuse people and make the whole system less comfortable to use. So we need something more flexible in this case.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

21,440 views 2 7
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you