-
Suggestion
-
Resolution: Won't Fix
I believe text areas where you write Markdown, such as in this very issue tracker, should use a monospace (fixed-width) font. This makes it easier to align stuff in code blocks and ASCII art diagrams and such. As a bonus, monospace also makes it easier to position the text cursor precisely using the mouse.
I can't find any scientific literature suggesting that monospace for text editing is objectively better (or worse), but I did take a brief look at what everyone else is doing.
First off, nearly all of us coders will be using a monospace font in our code editors.
StackOverflow, whose core business is having people write Markdown, and which strikes me as a pretty data-driven company, uses monospace (to be precise: Consolas,Menlo,Monaco,Lucida Console,Liberation Mono,DejaVu Sans Mono,Bitstream Vera Sans Mono,Courier New,monospace,sans-serif).
GitLab also uses monospace ("Menlo", "DejaVu Sans Mono", "Liberation Mono", "Consolas", "Ubuntu Mono", "Courier New", "andale mono", "lucida console", monospace).
GitHub does not use monospace. Rather than taking that as an example, I would see it as an opportunity where Bitbucket can do better 
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[BCLOUD-18036] Use fixed-width (monospace) font for Markdown editors
Hi everyone,
Thank you for bringing this suggestion to our attention.
As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.
Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.
While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.
Thank you again for providing valuable feedback to our team!
http://jira.atlassian.com/browse/BCLOUD-18036?focusedCommentId=2843995&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-2843995
Please do open this again, because I very much want to vote that this should be added, and I am sure that many others do. Occasionally, problems are greatly supported, but are not discovered for many reasons such as algorithmic determination of prominence. Your policy is surely rather illogical thus.