On 11/8/19 15:32, Ben Cotton wrote:
One weakness of the current editorial workflow is that there's
obvious way to indicate that an article needs a featured image. There
are four possibilities I see. What does the team think?
1. Create a new column
Advantages: Easy to see which articles need images so that people can
easily claim those.
Disadvantages: Adds another step to the flow and doesn't represent
well that images can be done in parallel to editing.
2. Use a tag
Advantages: Color coding means the card indicates the article needs an
image in most view.
Disadvantages: It's not clear what the color coding means unless you
3. Use a custom field
Advantages: Can have multiple choices to represent state (needed, in
Disadvantages: Not visible without opening the card
4. Use a task within the user story
Advantages: Can be assigned and have it's own state. We could also
potentially do the same for editing, though that might be redundant.
Disadvantages: Not visible without opening the card.
How about a combination of 2 and 3? You get the high visibility flag to
open the card and the state can be shown. The color could explained very
briefly at the top of the kanban page perhaps "Blue cards need image".
Have a Great Day!