mattflaschen wrote on 2014-04-23 05:23:11 (UTC)

Yes, we (Growth) use it for mini-tasks. Instead of making a separate task and noting it in the card as a dependency, we simply inline the dependency as a checklist item.

Checklists and items (an item is one of the lines of a checklist) are specifically *not* shareable between cards. If an item is a blocker for multiple cards, it should be its own card.

Interesting side note, Trello does not actually support dependencies. So even if there are cards for the main task and a dependency, a checklist is still a good way of visually indicating it (Trello also has a feature where if you put a Trello card URL, it is nicely formatted automatically, similar to Phabricator linking based on T=code, so you can just put a Trello URL as a checklist item)

Bottom line, it is a nice to have, but there is no clear rule for when it should be a checklist vs. a dependency, and we can get along without it.

qgil wrote on 2014-04-23 06:24:49 (UTC)

Thank you for the feedback. I will move it to the right column of the board, then.

Interestingly, I think I have found a little bug thanks to the checklist test in the description.

• T199 (correct)
• T199: Import non-test projects from fab.wmflabs.org to the official Wikimedia Phabricator (inconsistent, should have a strike)

Filed upstream: https://secure.phabricator.com/T4870

qgil wrote on 2014-04-23 15:21:14 (UTC)

Interesting, we might even get checklist syntax in Phabricator one day: T3945: Support Task List syntax in remarkup

See also T405: PhutilRemarkupRule for querying ApplicationSearch

qgil wrote on 2014-05-02 01:12:42 (UTC)

This task has been resolved upstream, taking only the rendering of the checkbox in read-only. They say that implementing read-write checklists is a very different story that takes a lot more effort. For us, it means an extra click to edit the task or the comment with the checklist.

See https://secure.phabricator.com/T3945. Screenshots available in the two related commits.

importing issue status

Checklists are used EXTENSIVELY, this will be a high priority feature for many teams switching from Trello

Do we need to create a separate read/write/rearrange/promote requirement for check lists functionality that mimics that of Trello?

In T116#14773, @Jaredzimmerman-WMF wrote:

Do we need to create a separate read/write/rearrange/promote requirement for check lists functionality that mimics that of Trello?

See T1141: Add Acceptance Criteria/Checklist feature to Phabricator tasks