Jira Description Markdown

As the Platinum Atlassian Solution partner, we have a team of certified Jira specialists. They are experienced in helping a variety of customers in configuring and using Jira. An essential part of helping our Jira customers is giving them insight into the correct use of Jira issue types. It has inspired us to write this blog, so that you can benefit from our best practices.

This blog is the 2nd part in the series on the use of Jira issue types (part 1 can be found here: on the topic of correct issue type use). In this blog we talk about how to manage issue types, sprints and backlogs in Jira.

At the project or global level go to Settings JIRA and set the sonar.jira.url, sonar.jira.login.secured and sonar.jira.password. JIRA Agile Essentials: Bring the power of Agile to Atlassian JIRA and run your projects efficiently with Scrum and Kanban Patrick Li download Z-Library. Download books for free. Jira confluence admin administration support script scriptrunner groovy mraddon barcelona plugin custom development it technology barcelonatech ethereum development. Download JIRA Assistant apk 1.0.0 for Android. JIRA assistant gives you access to your JIRA tickets with just a few touches.

How to apply issue types in Jira?

Below is a description of the default available issue types in Jira and what their most-used application is. Jira allows for other custom issue types like ‘Initiatives’ (also explained here), but this is out of the scope of this blog.

Jira Description Markdown

Also, for each issue type, different workflows can be applied. This can differ per client, but we often see different workflows per issue type. Where an Epic might have a more straightforward workflow (Todo, In Progress, Done), others might have more detailed workflows to cover all the scenarios.


Jira Markdown Syntax

Epics should be treated as large stories that do not fit in a single sprint or take longer to complete when not using scrum. It can span multiple projects and/or teams. Epics are different from the other issue types that it represents a group of related issues. There are also two dedicated reports: Epic Report and Epic Burndown to monitor the performance of your Epic(s).

Additional optionsmac guidance services. Epics are a special kind of issue type in Jira that are not visible on the backlog or boards. You can make them visible on scrum boards by configuring swimlanes. Epics are objects used for clustering and tracking the progress of it’s stories and tasks. Therefore, by default, do not show up in sprints as they’re a too big object to resolve in one sprint.

  • Epics consists of multiple issues, optionally from other projects
  • Issues are linked to an Epic, via the Epic Link
    • An Epic link differs from a regular link in a way that it describes a parent/child relation for one purpose
    • Allows to group issues via Epic linked issues
    • Rolls up time estimates of Epic linked issues
  • Are shown in the Backlog together with the release

Note that Epics are not placeholders for time-related items but always have a beginning and an end. For time-related items, you typically use Release (Fix/Versions) in Jira where you can define start- and end dates.

Tasks and Stories

The technical difference between tasks and stories is minimal. Depending on how you apply Jira for your product development a use-case can be made for using tasks and or stories.

From our experience, tasks are often left out since they are – technically from a Jira point of view – identical to Stories. Tasks would typically be an issue type for items that need to be planned but do not directly contribute to your product. From our experience companies define their own meaning for differentiating between Stories and Tasks.

With the introduction of Jira 7+ the issue types Improvement and New Feature where also introduced. They also have identical behavior and properties but only have different naming to describe their application. Because of this we will not address these issue types further on.


Out of the box sub-tasks do not contain the story point field. The idea behind this is to prevent micro-managing activities and so estimation should be done on a task level. Also note that sub-tasks behave in different ways then other issue types. Story points on sub-tasks are not taken into account and not displayed – by default – on the board. They are always related to a parent issue but can be defined at will.


The Bug issue type can be retained as it clearly defines a separate issue type that has its own use. It does have, by default, the Affect’s Versions and Environment fields attached to the screen but no link to the Epic.

They do not have the story points, by default, added to this issue type. The rationale is that bugs do not add customer value, as they show up unexpectedly and are not ranked. On the other hand one could argue that the fixing of bugs can be more accurately planned using story points.

If needed one could also choose to identify internal and external reported bugs. This could either be done by an unique issue type or defining fields.

Managing issue types in sprints and backlogs


For planning Epics, you would apply the Fix Version/s or Release fields. An Epic, by default, will not show up in the sprint but does get displayed in the kanban (as explained earlier). Epics can also contain issues from other projects as well. Keep in mind that issues from other projects in an Epic can not use the out-of-project Fix Version/s or Release fields. Delivery and releasing of the Epic is managed in the project where the Epic resides. Delivery and releasing of the Epics’ issues in other projects are managed in their respective projects. Atlassian has add-on for assisting with the alignment of multiproject issues in these Epics : Portfolio for Jira.

(Sub)Tasks and Stories

These issue types can be planned when needed. Subtasks are typically unplanned and not estimated as they can be created by team members to divide up the work.


On this topic, opinions differ. In practice, we see a lot of different approaches on how to manage bugs in sprints. Depending on the culture or approach in your company, your implementation can vary.

Below are some options we have come across; there is no right or wrong here.

Jira Description Markdown Template

  • An approach could be that solving bugs is planned in sprints. Example: 10% of the sprint time could typically be allocated for bug fixing. This means you would plan less than the reported Velocity in Jira.
  • Another could be to change scope, but this can impact the burndown. It can help to create a separate Kanban board to rank and prioritize bugs.
  • Add Story Points to bugs to overcome the problem of the reported Velocity in Jira.

Additional information on how bugs can be handled in Agile can be found here: https://www.scrum.org/forum/scrum-forum/6660/how-defects-should-be-handled-scrum. At TMC ALM we do not believe there is a one size fits all solution. We have assisted many companies in making the best decision on this topic. Of course we can advise you on what would be the most practical solution for your specific situation.

Contact TMC ALM

Do you also experience similar issues and don’t know how to solve them?

Contact TMC ALM for support or training on JIRA administration.

Details can be found on our website: https://www.tmcalm.nl/

The Atlassian editor supports markdown formatting for rich text fields. This makes it quick and easy to add headings, lists, code blocks, and more to your descriptions, comments, and other rich text fields.

Does Jira use Atlassian?

Q. How does the JIRA team use jira.atlassian.com? Ever since “JRA-1”, jira.atlassian.com (JAC) has been Atlassian (and JIRA’s) public issue tracker, with thousands of bugs, feature requests, improvements both raised and fixed. And up until 2009, JAC was actually where the JIRA team tracked all their work.

Should I use markdown?

Why You Should Use Markdown

You can quickly format text in any editor on any platform without even letting your mouse get in the way. It’s easy to learn and the results are easy to read. … Because Markdown is a superset of HTML, any HTML file is valid Markdown.

What is Markdown language used for?

Markdown is a lightweight markup language with plain-text-formatting syntax, created in 2004 by John Gruber and Aaron Swartz. Markdown is often used for formatting readme files, for writing messages in online discussion forums, and to create rich text using a plain text editor.

Can we use Jira for free?

We offer a Free plan for Jira Software for up to 10 users, 2GB of storage, and Community Support. If you’d like to add more than 10 users or get access to more support and storage, you can sign up for a 7-day free trial of our Standard or Premium plan.

Why is jira so popular?

Jira software is popular in the agile world due to its well-managed workflow mapping and issue tracking ability. To support agile development cycle it has Scrum and Kanban boards along with various reports.

Is Jira a good tool?

Atlassian’s JIRA began life as a bug-tracking tool. … Today, though, it has become an agile planning suite, “to plan, track, and release great software.” In many organizations it has become the primary map of software projects, the hub of all development, the infamous “source of truth.”

Is HTML a markdown?

Tags. In fact, Markdown has the software to convert the plain text to HTML built in! So Markdown is actually a text-to-HTML conversion software in addition to being a markup language.

Does Wikipedia use markdown?

There is a version 1.0 of the specification and several wikis and wiki engines implement it. MediaWiki does not implement it. Markdown has a large number of implementations and seems to be used quite a lot.

What is the markdown rate?

A markdown is an amount by which you decrease the selling price. The amount that you decrease the price by can be expressed as a percent of the selling price, known as the markdown rate.

What is difference between markup and markdown?

Markup is also referred to as margin or gross profit. The markup can be expressed as a percentage of the (1) cost or (2) selling price. This is known as the rate of markup. A markdown is a reduction in the regular selling price of a product.

What is markdown in coding?


Markdown is a lightweight markup language that you can use to add formatting elements to plaintext text documents. … When you create a Markdown-formatted file, you add Markdown syntax to the text to indicate which words and phrases should look different.

What is Markdown vs markup?

Markup is also referred to as margin or gross profit. The markup can be expressed as a percentage of the (1) cost or (2) selling price. This is known as the rate of markup. A markdown is a reduction in the regular selling price of a product.

What is better than Jira?

Let’s take a look at some JIRA alternatives.

  • ClickUp. Give ClickUp a try and you won’t have to deal with the JIRA Marketplace. …
  • Binfire. Binfire is a comprehensive project management application used by engineering and software teams. …
  • Basecamp. …
  • PivotalTracker. …
  • Asana. …
  • Clubhouse. …
  • Trello. …
  • ProofHub.

What is the best way to use Jira?

So without further ado, here are my 10 tricks to 10x your productivity in Jira.

  1. Use Filter Subscriptions as Reminders. …
  2. Create a Browser Search Engine. …
  3. Use Your Bookmarks Bar. …
  4. Use Keyboard Shortcuts. …
  5. Optimize Profile Settings. …
  6. Add Project and Navigation Links. …
  7. Connect to other Apps. …
  8. Get Read Only Database Access.

How do I start a job in Jira?

Getting started with Jira tutorial: 6 basic steps

  1. Step 1 – Create a project. In the top-left corner, click the Jira home icon ( , , , ). …
  2. Step 2 – Pick a template. …
  3. Step 3 – Set up your columns. …
  4. Step 4 – Create an issue. …
  5. Step 5 – Invite your team. …
  6. Step 6 – Move work forward.