Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Due Date for issues #2533

Closed
kolaente opened this issue Sep 17, 2017 · 1 comment · Fixed by #3794
Closed

Due Date for issues #2533

kolaente opened this issue Sep 17, 2017 · 1 comment · Fixed by #3794
Labels
type/feature Completely new functionality. Can only be merged if feature freeze is not active.
Milestone

Comments

@kolaente
Copy link
Member

It would be nice if one would be able to set a due date per issue, similar to how milestones can have a due date.

Sometimes you only need one feature to be done until a given date, so there is no need to create an extra milestone only for this.

@lafriks lafriks added the type/feature Completely new functionality. Can only be merged if feature freeze is not active. label Sep 17, 2017
@lafriks lafriks added this to the 1.x.x milestone Sep 17, 2017
lunny pushed a commit to go-gitea/go-sdk that referenced this issue Apr 17, 2018
* Added deadline for issue

* Added deadline for pull requests

* Added comment for swagger date format
@lunny lunny modified the milestones: 1.x.x, 1.5.0 May 17, 2018
@laoshaw
Copy link

laoshaw commented Aug 12, 2019

this is really useful feature, actually with starting/ending date and simple gantt support gitea can be better than gitlab and github and can replace redmine easily.

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/feature Completely new functionality. Can only be merged if feature freeze is not active.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants