Hacker News Reader

Comment by zmmmmm | Hacker News Reader

Wow. Hard to believe the pace at which this progresses and the quality that they pull off while doing it. Great job!

The only big thing I miss (and I miss this with Github too) is a way to prioritise issues. Yes, I get it, you can label things 10 different ways and achieve most of what you get from a priority system. It doesn't replace the simple ability to get a list in order of the most important things outstanding in order. I want it to be easy to generate a list of 'urgent' and 'high priority' where the 'urgent' issues are listed ahead of the 'high priority' and not ordered randomly.

View on HN

Priority labels aren't enough for you? (https://about.gitlab.com/2016/06/22/gitlab-8-9-released/#pri...) We're using P1, P2, etc. internally, but you could easily use `urgent` and `high priority` labels and then sort your lists by `Priority`.

Oh my goodness I didn't even know about those. I think it will address my needs perfectly. I will have to badger our systems people to upgrade.

Thankyou!

Great! Let us know if you have any feedback after you've tried them out.

I use milestones, for that. I almost never set a "due date". I find the milestone feature useful for doing, well, lot of not milestone related things.

First, they have a three columns (unstarted / started / completed) which adds easily simple trello-like boards to your projects.

Then, issues in those columns are sortable, like you describe, to prioritize. Simple drag'n'drop, could not get easier.

And finally, I use their description as a "release note". When MRs mention tasks to run on deploy, I'll just add them in milestone description, and I'll have a central doc for release.

Btw @sytse, would be cool if we could assign issues to several milestones. That way, we could use milestones as "view" for a given set of issues, each being ordered differently. This would allow different teams to have different prioritization, with a central issue hub. All of that by "just" allowing an issue to be in several milestones.

If you want this behaviour I recommend using labels instead of milestones. Currently an issue can be assigned to only one milestone and this is the first time I hear this request.

Oh, no, actually, I love handling everything through milestones, as mentioned in previous comment :)

Was just mentioning the idea in case you found it interesting to upgrade milestones to a project management tool. You already took github, travis and docker hub, I'm sure you can take trello as well ;) Go champs!

Great feedback! You might want to take a look at upcoming Issue Boards (https://gitlab.com/gitlab-org/gitlab-ce/issues/17907) and see if that works for you.

Oh, I see you already have us covered :D Looks great, will be awesome!

Actually consider you maintain two versions: 8.10.x and 8.11.x now a bug happens in both version to which milestone do you add the issue 8.10.2 or 8.11.2 even if the bug happens in both? ;)

Reply on news.ycombinator.com