# I want to code a kanban interface to categories .. lets put a spec together

**URL:** <https://meta.discourse.org/t/i-want-to-code-a-kanban-interface-to-categories-lets-put-a-spec-together/64306>\
**Category:** Feature\
**Created:** [Junho 11, 2017, 6:13am UTC](https://meta.discourse.org/t/i-want-to-code-a-kanban-interface-to-categories-lets-put-a-spec-together/64306 "2017-06-11T06:13:42Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)\
**Post date:** [Junho 12, 2017, 1:20am UTC](https://meta.discourse.org/t/i-want-to-code-a-kanban-interface-to-categories-lets-put-a-spec-together/64306/5 "2017-06-12T01:20:00Z")

</div>

> [@vikaskedia](#):
>
> There has to be a 1-to-1 relationship between the columns in the kanban and tags inside discourse.
> 
> How will I achieve this ?

Use specific tags for status. `s:new`, `s:planned`, `s:dev`, `s:test`, `s:released`. You could get around having a new of those tags by putting any closed topic into “Released”, any anything open and with a special tag into “Incoming”. As a sanity check/safety valve, if someone manually adds another tag (say they “move” the topic by adding `s:test` without removing `s:dev`), either put it into a (dynamically-created) “WTF?!?” column, or just leave it in both columns and have someone fix it up by hand when they notice one topic in two places.

Don’t let the perfect be the enemy of the good, here. You’re after a quick visualisation, not a strongly-consistent transactional distributed data store.

---

_[View the full topic](https://meta.discourse.org/t/i-want-to-code-a-kanban-interface-to-categories-lets-put-a-spec-together/64306)._