5 ms·

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, t

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.

oelmekki 10y ago
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.
- sytse 10y ago
  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.
  - oelmekki 10y ago
    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!
    - Snappy 10y ago
      Great feedback! You might want to take a look at upcoming Issue Boards (https://gitlab.com/gitlab-org/gitlab-ce/issues/17907 https://gitlab.com/gitlab-org/gitlab-ce/issues/17907) and see if that works for you.
      - oelmekki 10y ago
        Oh, I see you already have us covered :D Looks great, will be awesome!
  - merb 10y ago
    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? ;)

oelmekki 10y ago

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.

sytse 10y ago
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.
- oelmekki 10y ago
  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!
  - Snappy 10y ago
    Great feedback! You might want to take a look at upcoming Issue Boards (https://gitlab.com/gitlab-org/gitlab-ce/issues/17907 https://gitlab.com/gitlab-org/gitlab-ce/issues/17907) and see if that works for you.
    - oelmekki 10y ago
      Oh, I see you already have us covered :D Looks great, will be awesome!
- merb 10y ago
  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? ;)