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
Add start and due date to issue #2423
base: master
Are you sure you want to change the base?
Conversation
Thanks for your contribution as always! Though this pull request itself looks good to me, I would like to be careful to add new attributes to issues because I want to keep GitBucket core as simple as possible and offload additional functionalities to plugins. However, determining what functionalities should be implemented as core and what should be plugins is not easy stuff. Regarding Anyway, I want to hear opinion from users about this topic. Do you think adding |
@takezoe it depends, right now, the version that i have on my server it's the fastest, it that param is needed, or it's in github, for example, yes, put it.
If that plugin will be beneficial for several users, that's great and it should be put in the main, since it's only a param.... |
@takezoe GitBucket already includes the ability to assign things, set labels and priorities and track milestone times, so adding due dates lets you prioritize that way too and covers the use case of time-sensitive tasks. As for adding more fields to core, maybe? It kind of depends on their complexity I suppose. I'd like to have a Bugzilla-type issue blocking system so I can say 'this issue requires fixing A, B, C and blocks E, F, G' |
Thanks for your comments! I want to consider that a capability to add custom fields rather than adding some particular fields. Plugins will be able to leverage this capability to add required fields. As a result of this consideration, if we conclude that supporting custom fields is difficult, we will back to this idea again. |
@takezoe At first, I tried to implement |
I think it's a great idea to have this feature; In my case I'm using gitbucket in my company with a lot of plugins (kanban, network plugin) and having this feature will be beneficial for my team 👍 |
Hi , any news about this feature ? is is included as feature or plugin ? |
Hello @kasancode has this feature been merged ? |
My plan was to add an ability to define custom fields to issues and pull requests instead of adding specific fields. However, this plan hasn't made any progress due to the lack of our development resources. To be honest, considering our current poor development resources and the difficulty of implementing such a complex customizability, I started feeling that merging this might be more realistic. |
Custom field support is now in progress: #3034 |
Squash #2422
This PR add
start date
,due date
to issue.This PR will change GitBucket version number because of updating database schema.
If this PR is merged, I will implement gantt chart plugin supporting Future Task.
Before submitting a pull-request to GitBucket I have first: