Ok so it's not called Markdown, but that doesn't take away from the fact that there are two separate interfaces to accomplish relatively the same thing. Why would Atlassian choose to handle things differently between the applications? I'm most interested in the philosophy behind that decision.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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!
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