Why does https://about.gitlab.com/solutions/issueboard/ tell people to label issues first?
On https://about.gitlab.com/solutions/issueboard/, step www-gitlab-com#2 (closed) tells people to label their issue (and create a label), then in www-gitlab-com#4 (closed), create a list for that label. That feels wrong. I'd expect people to create labels specifically for the issue board, and add labels to issues by dragging them into the list.
For that matter, why not encourage them to use the default lists we provide?
Activity
Moved from www-gitlab-com#778 (closed)
Added Issue boards label
@axil correct me if I'm wrong, but my understanding of why we kept the flow of adding a label first was because we wanted to show the issue tracking functionality before jumping right into boards.
I agree with @amara.
Labelling an issue is a required step to work with Issue Boards. So, If we don't tell people to do that, the issues will stay in the backlog.
For the default labels, I don't think we need to encourage people to use them. Every workflow is different, the cool stuff is the ability to organize them according to our needs.
Also:
I'd expect people to create labels specifically for the issue board
Not necessarily, I think this is up to each person to do or not. They will figure out how to label their issues in a way to help them with their own workflow. For example, for devs, the workflow will most likely be completely different to the ones we use for marketing.
Derp, I forgot to link to the discussion that already took place. @markpundsack check https://gitlab.com/gitlab-com/marketing/issues/400#note_13834760 until my first reply.
Hmm.. read through that thread, and still don't get it. :)
Labelling an issue is a required step to work with Issue Boards.
Perhaps this is the crux of it. Since moving an issue from the backlog to a list adds the label for you, I don't think users even have to be aware of labels outside of that context in order to use the Issue Boards.
So, If we don't tell people to do that, the issues will stay in the backlog.
This, imho, is false. :) That's why we support drag-and-drop between lists.
It's quite feasible that someone would only use labels for the board and never use them otherwise. In fact, under that circumstance, other than the admin that configured the lists, the users wouldn't even see labels at all.
While I think it's good for users to know about labels, it feels wrong and unnecessary in this context to have them use them outside of the issue board. And it's missing an opportunity to show the true value of the board, which is dragging something from the backlog and putting it into a list. Of course you do cover drag-drop in step #5 (closed).
I just noticed that step 2's title says to "Label your issue", but the step content doesn't actually cover applying the label to the issue.
IMHO, I think creating the label would be better suited to part of step 4 because you can create a new label as part of creating a new list.
Added solutions label
