This looks like a great start. I'd like to take a step back from the visual design of this and think a bit about the interaction. I have a few things that I'd like us all to discuss:
- Do we let people turn this off? I can see a lot of people who don't care just wanting to get rid of the thing blocking their view. Do we have it off by default?
- I can see in all of your mockups how new items are added. If I add something and then change my mind, how do I remove it? How do I edit it? You may want to play with Asana for a few minutes for some inspiration here :)
- It would be nice to be able to define some kind of template, so I don't have to type out all of my checklist items every time. Similarly, team leads or managers might want to maintain an "official" checklist for everyone to use. How do I define a template? How do I share it?
- If I mistakenly use a template (or make some other mistake), how can that action be un-done?
Mockups for Checklist Extension
Review Request #4668 — Created Sept. 30, 2013 and discarded
First draft of mockups for the checklist extension. I wrote more details on hackpad: https://reviewboard.hackpad.com/Checklist-Extension-Hwc1QKe03kw. The three designs are similar in functionality, but different in looks. The first is pretty basic and simple; the second is semi-transparent; and the third is based off of the RB logo.
There is 1 minor and 2 major updates for the mock-ups:
1) Regarding the old design, we can edit checklist items by clicking on them. We can type a new item and click 'Edit'. Or we can remove the item by clicking 'Delete'.
The major updates pertain to the use of Templates. I was thinking about how we can allow the use of updates in an easy manner.
2) While reviewing, a reviewer can choose to use templates for their current checklist by using the Template Dialog (opened by clicking 'Use Template'). I'm debating whether the templates should be used in their entirety, or we should allow reviewers to choose particular items from the templates. Currently, my mock-ups depict the latter, where reviewers can pick and choose items from templates. Adding at least one item from a template marks the template as 'In-Use' (marked by the * symbol). The user can also update their choices by reselecting/deselecting items from the template.
3) I also think we need an overall Checklist Manager for each user. Here they can create their own configurations, like using checklists or not, create new templates, edit templates and share them with others.
Oh, and currently, the Template Dialog in the Reviews page shouldn't allow users to edit a template. They can only edit the current checklist by adding items from templates, or using templates in their entirety. The place to edit templates is only in the Checklist Manager.
Nice sketches! They really help to convey what you're thinking about, so mission accomplished. :)
I have a few small concerns:
Primarily, I worry that the idea of templates might be a bit ambitious for a first iteration on this extension. I think we might get bogged down if we try to do too much at once. I like the idea of templates, but I think maybe we should shelve it for a bit, and try to get the simplest (yet still useful) interaction completed first, and then expand out from there.
I also have a few small suggestions for how to do inline-adding/removing of items in the checklist - see my other comments.
That's a lot of space for these two operations.
What happens if instead of these two large buttons, you have "X"'s right-aligned after the checklist item name for removal?
And then a "+" where a checkbox would go in an empty row below the last item, which when clicked, would display a text input and an OK and Cancel button (like the fields in a review request) for adding a new item?