Set due date for individual issues

Report http://feedback.gitlab.com/forums/176466-deprecated-feedback-forum/suggestions/6239210-set-due-dates-for-individual-issues

and @AshleyS really want this to move from Asana

I don't think that requiring that people make a milestone is a good alternative, it takes a lot of time to create one.

/cc @dzaporozhets @JobV

Let's do this. cc @dzaporozhets

I propose to:

• make it optional, a project setting
• immediately add it to the issue list and add a filter for it (otherwise the usability is too lacking, something we learned with votes)
• start with a simple date picker

@creamzy could you create a mockup whenever you have time?

Added ~122770 label

Added feature proposal label

Added ~19492 label

scheduled for 8.6 for mockup. Implementation time will be decided at a later point.

Milestone changed to 8.6

immediately add it to the issue list and add a filter for it

@JobV adding another filter is not an option. No such space in UI. Also collecting all custom milestones from all issues is performance issue.

make it optional, a project setting

@JobV lets make it a default feature.

@dzaporozhets sorting option :), not filter

sorting option :), not filter

@JobV deal.

make it optional, a project setting

do you agree making it integrated instead of optional/setting ?

@dzaporozhets yes, I didn't feel strongly about it.

@JobV I think everything should be default. If you want to make something a setting please elaborate what and why.

@JobV

start with a simple date picker

due date should depend on milestone due date, should we show only available time slots?

due date should depend on milestone due date

I think due date should not be depended on milestone due date. I think its unnecessary limitation

I think due date should not be depended on milestone due date. I think its unnecessary limitation

I agree.

@sytses as said, I didn't feel strongly about it and am fine with adding it by default.

My thinking was that a due date on issues encourages the user to use a bad workflow, where every issue is scheduled individually. In 80% of cases, they are better off using a milestone. Due date on issues is super convenient, but you should really be looking for it, rather than using it because it's available.

@JobV I'm really afraid of what happens to the UI if we add optional fields that we don't test with.

@sytses

Side note: I think the sidebar is an excellent place for optional features, as they would just be added in the list. I especially like the way Trello does this, to which we're now quite close.

@creamzy Can you work on a mockup, ideally this week, so we can start on backend implementation soon?

@DouweM me or @skyruler will ship it this week :thumbs_up_reverse:

Reassigned to @skyruler

@skyruler Nice! I see you've assigned yourself, is there something you still want to do, or is it time for a developer to hop in?

@DouweM I'll put fronted and dev labels

Removed ~19492 label

Added frontend label

Added ~123454 label

Assignee removed

Status changed to closed

Status changed to reopened

Sorry I closed the issue by mistake. I think a prerequisite to this issue is the new dropdowns which @iamphill is working on.

@jschatz1 Do you have an issue for that?

@DouweM https://gitlab.com/gitlab-org/gitlab-ce/issues/3279

Added ~164274 label

mentioned in merge request !3160 (closed)

Backend is being worked on in !3160 (closed)

Milestone changed to 8.7

This is not gonna make 8.6, but work has already started on the backend development. I will move it to 8.7.

@DouweM is the backend ready? Like enough that we can use it?

@jschatz1 Yep, if you stick to the frontend you can build on https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3160. The most important pieces are the due_date field on Issue, and the selectboxes in the issue filter bar and the issue sidebar.

mentioned in merge request !3614 (merged)

Status changed to closed by commit 91c00fae

mentioned in commit 91c00fae

mentioned in commit 82d8c74f

mentioned in issue #15663 (moved)

mentioned in issue #27500 (moved)

mentioned in issue gitlab#4769

mentioned in issue gitlab#8077