.png)
%20(5).png)
Issue Checklist for Jira - Free
Add ToDo list to Jira issues with one click. Create and reuse Templates. Add default checklists to new issues automatically
Get it NowCloud
Free!
June 1, 2018
28000
No setup required
Just install and you're ready to go. Open an issue and start adding ToDo items. Split the issue into lightweight sub-tasks and visualize their progress. Works in Classic and Next-Gen projects. Available in agile boards too.
Work with templates
Save a checklist as a template and load it any time you need. Make the template a default one to load it automatically when issues are created.Useful for Definition of Done, Acceptance Criteria and recurring processes.
Use mentions, due dates, emoji and Markdown
Discover more advanced features when you need them: mention user, add due date and multiline description, insert issue keys, hyperlinks, emoji, and Markdown formatting.Add multiple checklists to organize items.
More Details
Try it FreeHighlights:
- Use this limited free version of Issue Checklist Pro to
- split Jira stories into lightweight ToDo items and watch the progress as they become completed.
- Highlights:
- View-Edit checklist from issue view, agile board, Jira mobile app or REST API
- Create checklist templates and load items from a template any time
- Set a default checklist for a project and issue type
- Use headers or separate lists to group items
- Use statuses like "In Progress" and "Skipped"
- Block issue transition if checklist is not completed
- Multiline descriptions
- User mentions, due dates , issue keys and more
- Use Markdown editor
- Enable / disable checklist per project
- Clone checklist with an issue
- Copy-paste checklist as a text
- Convert checklist item to Jira issue
- Track checklist changes
- Search for checklist items with JQL
- Integrate with automation tools
- Edit concurrently in multiple windows
- Available in multiple languages
- More
It is a free version of Issue Checklist Pro. It comes with documented limitations
Questions or feedback? Contact us via service desk or support@herocoders.com.
Frequently Asked Questions
What is the difference between Pro & Free ?
We explain the difference on the following documentation page: Free vs Paid subscription.
How can I buy Issue Checklist Pro?
Atlassian is responsible for handling subscriptions and payments (vendors only set per-user price). It should be enough to just start the trial.
Where can I find Privacy Policy, Security Statement and Terms of Use documents?
Can the Issue Checklist slow down my Jira?
No.
Issue Checklist and all other add-ons for Jira Cloud (as opposed to Jira Server plugins) are loaded in separate iframes inside the Jira page. This approach ensures security (iframe code cannot access the main page) but also lets the browser load the content of the add-on asynchronously without blocking the main page.
Are there any limits on the paid version?
There are no limits at all. You can add as many items and templates and as often as you want
How much (and for how many users) will I pay for Issue Checklist Pro?
Atlassian is responsible for counting a number of users. It usually equals the number of users registered in your Jira (excluding Service Desk customers).
Frequently Asked Questions
Are the Cloud and on-premise (Server and Data Center) versions identical?
The on-premise version is implemented via a new Custom Field Type, while the cloud version is a Connect App. Since Atlassian does not allow third-party Custom Fields on their cloud instances, on-premise and cloud Apps have different architectures and integration points in Jira.
Their feature set is a little different, but as Atlassian improves its Connect API, both versions are becoming more and more similar. Read more about comparison here.
Why do I need to first create a custom field in the Server and Data Center versions?
Checklist for Jira Server and Data Center versions have been developed as a custom field since it offers a much tighter integration into Jira.
It allows more features like viewing checklists in the Create, Edit or Transition screens or bulk updating the checklist of many issues at once.
Don’t worry; adding a Checklist custom field is fast and straightforward.
What if I don’t need all the checklist features?
Checklist for Jira is highly configurable to meet a variety of needs as no two organizations work the same way. Use only the features you need. As your needs to grow, Checklist for Jira can grow with you.
How can I best implement Definition of Done (DoD) and Acceptance Criteria (AC) in Jira?
Read this blog post we wrote.
Will I lose my data if I uninstall the app or my trial ends?
For Cloud, we keep the data for one year as some clients repurchase Checklist for Jira. But if you want us to completely remove your data, please open a support ticket.
As for the Server and Data Center, the data stays until you delete the Checklist Custom Field.
I like Checklist for Jira, but can I buy it only for a subset of users?
Unfortunately, Atlassian does not allow this and we are required to follow Atlassian licensing rules. All Atlassian Marketplace apps must match (or exceed) the parent product in terms of user tier.
What this means is that you need to buy the same user tier for any app that you have for the host product (example Jira).
Frequently Asked Questions
When are automatic timers started / stopped?
Automatic timers are started and stopped according to the current workflow your project uses. To learn more read When do automatic timers start / stop?
Is it compatible with Tempo?
Yes, Clockwork works with Tempo as well, but our plan for the future is to offer similar features that you won't be needing Tempo.
How sub-tasks are handled?
When working on a sub-task time spent is reported only on the sub-task. Parent issue is not updated so you should not keep the sub-task and the parent issue in progress at the same time.
How does it calculate time worked?
If you want to know more about the way we calculate time please check out How time spent is calculated (with working hours)?
When time is logged into Jira?
Time spent on the issue is logged only once the timer is stopped. It means that currently Clockwork will log all time spent at the last day. It will not spread the time through days the timer was running.