Issue boards as a top level menu item

Yes please, same here - need to get more traction around GitLab by making Kanban a first class citizen.

added ~19492 ~14213 ~579196 labels

I don't know if this deserves a separate feature proposal or if this one is similar.

Here is the use case we have:

We have one service, with back-end modules, a portal, and SDKs;
These modules use separate "Projects";
Product wise, we want to be able to use the Issue Board to stop having to use a separate tool to create stories and track issues;
It seems however that Issue Boards don't span a group or more than one Project;
BUT some features/stories related to more than one module so they need to include multiple projects;

E.G. of a story:

Tongdao now supports rich media notifications in Android: spans our Android SDK, our Messenger module for handling message sending, and portal for the user to input the data.

Current workflow would be: create a story mostly similar in three different projects and keep track of these three stories. --> Painful.

@florian-monfort that's certainly a use case I've come across a lot (in fact, more often than not). ZenHub solves this for GitHub by providing the ability to "merge boards" from different projects and the support for "Epics" (where a master issue can contain child issues from other repos).

imho: I think your proposal warrants raising a separate issue.

I can see that GitLab CE are considering "Epics" here - https://gitlab.com/gitlab-org/gitlab-ce/issues/20135 and I think there are some great ideas on this.

@junketjim weeeelllll....

I think my point is right now that maybe we should add this as a feature request especially for Enterprise Edition because we would definitely pay for it...

The thing is though, so far these are the only two things that we're missing that prevent us from coming from Jira. The workarounds are just painful.