How to Easily Create Checklists in Jira


Diesen Artikel auf Deutsch lesen

If you’ve been a Jira Cloud user for any length of time, you know the drill; tickets get created with deadlines or within specific sprints, those tickets get assigned, work gets done and recorded, tickets are updated and (hopefully) closed. There can be nuances but in a nutshell, that’s how the process basically works - project, after project, after project.

Why reinvent the wheel if this system seems to work for everyone? Oh, but does it truly? Each issue type, be it a story, task, bug, epic, or subtask most often includes a number of ancillary, routine tasks. In other words, it’s not just about completing X, Y, and Z, it often involves X1, X1a, Y1, Y2, etc. And with every story or bug, these ancillary tasks are often the same every time.

For example, if the task is “Clean bathroom”, the assignee might be expected to empty the bin and clean the shower door as part of that. But if it’s not in the ticket, who knows if they are? It means that everybody ends up with their own idea of what’s considered “done” because conventional Jira processes don’t capture the detail.

Checklists in Jira make sure everything gets done

How to Easily Create Checklists in Jira - Atlassian Ecosphere

You may say to yourself, “We already use Jira Cloud. When an issue is marked ‘done’, it’s done, right?” As humans, we love to either completely simplify something or overcomplicate it. Simplifying in that sometimes we just want to get a task off our plate and move onto the next thing. Other times, we want checks and double checks, and a triple check just for good measure.

Why can’t we just enable a process just once that allows us to say, “Yup, we can all agree, this is now done and everyone agrees what that means”? Well, this is exactly what checklists are for – making sure that all the routine, ancillary tasks are completed for the main task to be considered “done”.

This is where Didit Checklists for Jira comes in. The premise of Didit is simple: be transparent, be consistent, make it easy, reduce errors, and as a result the level of quality improves. It provides accountability that is easy to design for without adding unnecessary complexity or burden to your users. It ensures reliable completion of repetitive business processes.

We’ll discuss how you can easily embed Didit checklists into your Jira Cloud instance, and how to use public checklists on the go with our iOS and Android mobile apps. It’s also not tied to only your internal users as it can be shared via a QR code offering both public and private checklists.

How to embed checklists into your Jira tickets


Jira Cloud is a phenomenal tool for teams working collaboratively to complete projects and developments tasks of all types. However it can accidentally leave the door open to human nature and subjectivity. David in QA contends the task he and his team have been working on is complete based on the Jira Cloud ticket just as it’s written. However, Sarah the PM counters there’s always two specific loose ends that always seem to get missed.

What’s the best way to keep David and Sarah from tearing apart that work-buddy relationship where they make an espresso run at 2:20pm every afternoon together? Integrate Didit Checklists for Jira into your Jira Cloud instance so the finer details of every project are easily and seamlessly woven into the processes. Now everyone can agree when the task is complete. Heck, David can use the Android or iOS Didit app on the way to the cafe, and Sarah can see those inevitable two loose ends are actually done when she’s back at her desk at 2:35pm.

With Didit, you can automatically embed any of your existing checklist templates into a new Jira ticket. You can even specify one template for an epic, but a different one for your tasks, and yet another for each story. If your problem is that there’s currently no consensus on when something is done, then you can create a “definition of done” (DoD) checklist template and embed it into every new task you create.

Software developers already know the importance of agreeing a DoD, which is why a DoD template for software development comes with the Didit app. Simply add the template to your instance and tweak it to match your team’s criteria.

how to easily create checklists in Jira - embed Didit Checklist in new tasks

A rundown of what you can do with Didit checklists for Jira


If you need to quickly share a link to one of your checklists through one of the many messenger apps you might be using in your daily work, simply copy the checklist URL, paste, and send. There’s a slew of functionality already built into Didit with more on the way. We’re always open to feature requests.

Here’s a quick look at our feature set:

  • Create new and fill out checklists in Jira
    • Use the integrated Jira ticket checklist to create a new checklist out of a template or fill out existing checklists within a Jira task.
  • Templates
    • Templates serve as a template for recurring, standardized checklists. Use templates to always assign the most current and correct version of a checklist to the right people.
  • Jira auto-assign checklist
    • Auto-assign a specific checklist to an issue type in Jira Cloud in your project settings.
  • Use Didit with Jira automation
    • Configure triggers such as Didit creating a new Jira issue when a task is checked. Configure actions such automatically adding a checklist to an issue once it transitions.
  • Make multi-checklist reports for tracking and auditing
    • Export multiple checklists as a single PDF report, which is useful for compliance, audit preparation, and just generally checking on progress. Use filters to capture the exact insights you need.
  • Share your checklist via QR code
    • Generate QR codes that can easily be scanned with every smartphone and used without requiring a login.
  • Public checklists
    • Share checklists outside the Atlassian Cloud through public links.
  • Mobile app
    • Use our native mobile app for iOS and Android to create new checklists or complete started ones.
  • Always in sync
    • Your checklists always stay in sync between Jira, the mobile app, and our standalone web portal. And if you have Didit for Confluence as well, your checklists are synced between your Jira and Confluence instances.
  • Allow external users to access your checklists
    • With our in-sync standalone portal, external users can register and use Didit, be assigned as Template Managers, and thus can manage checklists and templates without the need of an being an Atlassian user.

Want to start using checklists in Jira?

If you’re chomping at the bit to get going with Didit Checklists for Jira, and to extend it through your entire Atlassian ecosphere as well as using the mobile apps, you can jump right into all the features documented here.

You can also schedule a personal demo or chat with us about your checklist needs.

Further Reading

Forget Less and Ensure Quality with didit Checklists for Atlassian Cloud Forget Less and Ensure Quality with didit Checklists for Atlassian Cloud Forget Less and Ensure Quality with didit Checklists for Atlassian Cloud