Milestones
Created by: dzaporozhets
- Separate entity with scaffold
- Ability to attach different resources like Issue, MR, git tags
Activity
Created by: superbobry
Well, I guess @randx is talking about implementing GitHub-style milestones for GitLab; but still -- it would be nice to have a checklist with things that need to be done.
By Administrator on 2012-01-26T20:29:29 (imported from GitLab project)
By Administrator on 2012-01-26T20:29:29 (imported from GitLab)
Created by: lhaig
I agree. I was getting confused as to what these issues were. Now I know they are features for 2.2 I think it is a great idea I like the checklist option as it would make it easy to spot stuff that needs to be done
By Administrator on 2012-01-26T20:31:42 (imported from GitLab project)
By Administrator on 2012-01-26T20:31:42 (imported from GitLab)
Created by: cweagans
I started looking at this tonight and tried to start coding up a solution. Unfortunately, my Ruby is a little rusty (read: I'm terrible at it). So instead of a poorly written patch, I'll provide information about the design details.
The first thing that I did was create the concept of "Features" that can be toggled on a per-project basis. Next, I added a little configuration page that allowed toggling features for each project. The features that I allowed toggling are:
- Issues
- Network Graph
- Milestones
- Wall
This way, functionality that is not needed for a project can be disabled by an administrator. I did not allow disabling the repository viewer because it seems like sort of a critical part of a project and it doesn't make sense to disable it.
Next, I created the Milestone data structure. A milestone belongs to a project, and has these fields:
- Title
- Description
- (Optional) Responsible User (who is responsible for the completion of this milestone?)
- (Optional) Due Date (my plan was to use the jQuery date picker for this)
Finally, I created a page that allows for listing milestones in a project (this is displayed as a tab right below "Issues" on project pages). This listing was ordered by due date, with the milestones due soonest at the top.
The things that I didn't get to:
- Associating an issue with a milestone. An issue should only be able to be associated with one Milestone. This will cover most of the use cases, and will reduce complexity of the code.
- Drag and Drop issue sorting (the idea here is that you'd get a list of milestones in a box on the issue listing page, and the default view for the issue listing page would display issues not associated with any milestone. Dragging and dropping an issue onto a milestone associates that issue with the milestone and that issue is removed from the listing)
Future tasks that might complement this feature:
- Issue #344 (closed) (Providing issue states - would allow for a very nice Scrum workflow in Gitlab)
By Administrator on 2012-01-27T04:38:40 (imported from GitLab project)
By Administrator on 2012-01-27T04:38:40 (imported from GitLab)
Created by: dresende
+1. I just deployed gitlab and loved it. The thing I miss the most comparing to github is the Issues zone. I like the labeling and milestones. I think improving the Issues would really make gitlab a great free alternative to github.
By Administrator on 2012-02-22T17:08:24 (imported from GitLab project)
By Administrator on 2012-02-22T17:08:24 (imported from GitLab)
Created by: franzliedke
+1
Oh yes, improving the ticket system is a must. And not all that hard to do. Milestones is a very important first step. Also, simple labels would be perfect for more structuring.
By Administrator on 2012-03-14T22:38:59 (imported from GitLab project)
By Administrator on 2012-03-14T22:38:59 (imported from GitLab)
Created by: mikkyhouse
@ariejan do you want to take this feature?
By Administrator on 2012-03-15T10:44:34 (imported from GitLab project)
By Administrator on 2012-03-15T10:44:34 (imported from GitLab)
Created by: ariejan
@mikkyhouse it's already assigned to @vsizov. Not sure what his status is. I'm not sure if I have enough time to finish this before the 22nd.
By Administrator on 2012-03-15T11:16:58 (imported from GitLab project)
By Administrator on 2012-03-15T11:16:58 (imported from GitLab)
Created by: dubcanada
This might be a bit much to have done before the 22nd. However I could probably have it done if not before shortly after the 22nd. If @ariejan doesn't want to do it. I was working on the network graph.
By Administrator on 2012-03-16T12:57:57 (imported from GitLab project)
By Administrator on 2012-03-16T12:57:57 (imported from GitLab)
Created by: dubcanada
Just a note, I started working on this. I'm going to do labels first, as I feel that would be the first stepping stone. As well as cleaning up the whole issue area.
By Administrator on 2012-03-17T05:12:29 (imported from GitLab project)
By Administrator on 2012-03-17T05:12:29 (imported from GitLab)
Created by: dubcanada
I spent all of maybe 15 minutes doing a rough design. This is really rough, so I apologize a head of time. I'm trying to not change much about gitlabhq, while trying to create a much more expandable issues area and not cloning github. It's actually a bit hard to do. Opinions and ideas welcome...
By Administrator on 2012-03-17T06:36:24 (imported from GitLab project)
By Administrator on 2012-03-17T06:36:24 (imported from GitLab)
Created by: dzaporozhets
@dubcanada Your task is pretty hard but lets follow gitlab design. I like a concept but gray frame for comment is not ok. Lets keep UI clean and pretty
By Administrator on 2012-03-17T14:36:12 (imported from GitLab project)
By Administrator on 2012-03-17T14:36:12 (imported from GitLab)
Created by: dubcanada
I decided to just leave most of the stuff as is for now and get the functionality done. I am at http://markup.io/v/vj34dg629tnp for a final layout.
New issue page (this doesn't include milestone stuff yet). http://markup.io/v/7vtq7f6d4wnm
Issues list page http://markup.io/v/r7kg9nwqkz7g (there is some extra comments for future ideas).
By Administrator on 2012-03-20T00:13:46 (imported from GitLab project)
By Administrator on 2012-03-20T00:13:46 (imported from GitLab)
Created by: rtripault
Some food for thoughts…
Actually, it seems that a milestone without due date or which due date is over is considered as "inactive". Shouldn't it be possible to have an active milestone without a clear/defined due date or being late in a milestone while it is still considered as an "active" one ?
As usual, thanks for you hard work guys!
By Administrator on 2012-04-09T11:12:55 (imported from GitLab project)
By Administrator on 2012-04-09T11:12:55 (imported from GitLab)
Created by: jameswritescode
Currently if you do not choose a due date, the due_date is set to NULL and it shows as inactive in the milestones listing. Is it possible to make it show as active if no due date is specified and make it optional?
- edit: rewording
- edit: submitted pull request to https://github.com/gitlabhq/gitlabhq/pull/698 regarding this
By Administrator on 2012-04-19T18:29:53 (imported from GitLab project)
By Administrator on 2012-04-19T18:29:53 (imported from GitLab)
