You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

JIRA has a built-in Checklist field type, but it's pretty basic. Sometimes you want something more like JIRA's Task List macro.

  • Show all checkboxes, even if unchecked, rather than hiding unchecked items as JIRA's Checkbox field does.
  • Show a mini completion status (X of Y checkboxes ticked).
  • Let users add new checkbox items dynamically.

Plugin vendors have tried to fill the gap. Here we compare a few, Checklist for JIRA, Kanoah Checklist and the free ToDo list custom field, seeing how they stack up to each other and the built-in Checkbox field.

 JIRA CheckboxesChecklist for JIRA

Kanoah Checklist

ToDo list custom fieldIssue Checklist
 Built-inMarketplace ListingMarketplace ListingMarketplace ListingMarketplace Listing
Price (Feb '16)$0

10 / 35 / 75 / 150 / 325 / 480 / 650 / 875 / 950

10 / 25 / 50 / 100 / 250 / 275 / 325 / 325$0$0
Support 

Via answers.atlassian.com Q&A. This is good in that prior questions answered become a form of knowledge base.

Via JIRA on https://kanoah.atlassian.netVia answers.atlassian.com Q&A 
Issue View

 

By default only the first two checkboxes are shown – even if other hidden ones are checked:

Fortunately this behaviour can be turned off, showing all checkboxes:

Strikethrough can also be turned off.

 

  
All Checkboxes Ticked 
Edit View

Note the stars, indicating 'required' fields.

Note the ability to edit/delete items on the fly

 

 
List View

 
Structure View

 
Searchability

 

 

 

 

 
Configuration

\

Options are not managed centrally, but rather per-issue. New issues acquire the Default Value:

Options are not managed centrally, but rather per-issue. New issues acquire the Default Value.

Due to what seems like a bug, the Default Value doesn't display:

until one clicks 'Edit Default Value':

 
Customizability

n/a

  • Strike through is optional
  • Items can be made 'mandatory', towards a 'Completed' field status.
  • Addition of new items can be restricted by role

n/an/a 
Internal Database Representation

customfieldvalue.stringvalue stores ID references to predefined options:

11202
11201
11200

customfieldvalue.textvalue stores JSON records (one per checkbox), referring to a predefined option.

{"checked":false,"name":"","mandatory":true,"rank":5,"optionId":11215,"version":"3.0","id":11215,"statusId":"none"}{"checked":false,"name":"","mandatory":true,"rank":4,"optionId":11214,"version":"3.0","id":11214,"statusId":"none"}{"checked":false,"name":"","mandatory":true,"rank":3,"optionId":11213,"version":"3.0","id":11213,"statusId":"none"}{"checked":true,"name":"","mandatory":true,"rank":2,"optionId":11212,"version":"3.0","id":11212,"statusId":"none"}{"checked":true,"name":"","mandatory":true,"rank":1,"optionId":11211,"version":"3.0","id":11211,"statusId":"none"}{"checked":true,"name":"","mandatory":false,"rank":0,"optionId":11210,"version":"3.0","id":11210,"statusId":"none"}

customfieldvalue.textvalue stores one JSON field per issue, with direct option values:

[{"description":"Overview Doc Written","checked":true},{"description":"High Level User Stories Written","checked":true},{"description":"UX Design Developed","checked":true},{"description":"Eng Tech Spec Written","checked":false},{"description":"Eng t-shirt Size & Quarter Commit","checked":false},{"description":"All Sprints Scheduled","checked":false},{"description":"All Code Checked In & Tested","checked":false}]

customfield.textvalue stores one JSON field per issue, with direct option values:

[{"id":"Overview Doc Written","type":"done"},{"id":"High Level User Stories Written","type":"done"},{"id":"UX Design Developed","type":"done"},{"id":"Eng Tech Spec Written","type":"todo"},{"id":"Eng t-shirt Size & Quarter Commit","type":"todo"},{"id":"All Sprints Scheduled","type":"todo"}]

 
   Once an issue is created, its options vary completely independently of any other. You can create new checkboxes on the fly within the issue. You cannot bulk-change the wording of a checkbox across issues.  

Conclusion

 

  • No labels