Well, Markdown actually. What I mean is, you can now use Mark down to mark up your descriptions in Agilebuddy.
So any time you see this, it means you can use markup:
You can click the Markdown link to view a cheat sheet of the syntax.
Here’s a little sample of what’s now possible in a bug description:
A change we had to make to accommodate markup was add Title fields to user stories and tasks. Since descriptions now support markup, displaying marked up text in a backlog view doesn’t look very good. So we needed every item to have a non-marked-up field that we could display in backlogs. You can view the description by clicking the more… link or going to the details page for that item. Titles are required and descriptions are now optional. Note that bugs already worked this way.
Existing user story and task descriptions have been moved to the title field for you.
For API users: titles are now a required attribute when creating user stories. We’ve made the API backwards compatible so that if you have a client only sending the description, we’ll simply use it as the title instead. Note that the title has a 255 character limit though, so we urge you to update your clients appropriately.
Home | Features | Tour | Resources | Signup
About Us | User Guide | Consulting | 