If you need more freedom in assigning the checklist automatically, you can choose to automate it with a JQL filter, by clicking on "Automate with JQL Filter". Project templates can only be added to the project they belong to. Please note that if you are automating a project template, you will not be able to select any other projects. You can then select specific projects and issue types, that will have the selected template automatically added as a checklist to each created issue of those types. Provided you are a project admin or Jira instance admin, you can click on “Automate template” after selecting a template name from the list. The last one is only available if you administer at least one project on the given Jira instance. The screen allows you to edit and delete the existing templates, as well as assign them to be automatically added to the newly created issues. You can access template management either directly from any Jira issue, through Multiple Checklists for Jira options, or via Jira Settings, provided you are the instance administrator. Don’t worry, you can always edit the template later on, by adding more items, editing existing ones, reordering them, or deleting. Once you have done so, just click “Save” and your template will be saved. You will be prompted to enter a unique name for the template. Once you are happy with the result, click the “Save as template” button from the menu next to the checklist.
#ISSUE CHECKLIST PRO HOW TO#
Wouldn't it be great if after entering your Jira issue, you could see right away the complete list of criteria that you have to fulfill? This guide explains step by step how to achieve this with Multiple Checklists for Jira - an Atlassian Marketplace app available for Jira Cloud and Jira Server.Įnter any of your Jira issues and start working on your checklist items. Still, human memory is faulty which makes it hard to remember every single step on your path to success (or "Done" if you prefer). You have to stand up to these standards because you want to deliver the highest quality service or product, of course. The thing about all those mentioned situations is that they all concern universal requirements that apply to the majority of the tasks you and your team face.
That may include making sure the bugs have reproduction steps included or that new features have acceptance criteria. Another common case is tracking whether the ticket is ready for development. One typical use case is having the “Definition of Done” available by default in each new issue, to make sure that either developers or testers take time to verify if the task is done by the definition the team agreed to follow. Automatically adding checklists to each new Jira issue is a desired functionality.
0 kommentar(er)
