Dynamic or new Issues status

[Paymanonline]

I think We need ability to create new status.
Or at least we need four status
new: when a new issue create.
opened: when a user start working on an issue
resolves: when a user finish working on an issue
closed: when issue merged with main branch

issues can be filtered with every status and users can change issues status. also issue has to resolved when a commit come with message Resolves #IssueNumber

[onukura]

I'm not sure if I understand what you mean, but maybe it can be possible with
gitbucket-label-kanban-plugin.
You can manage each issue status by label (you should change label manually).

[takezoe]

Also, I'm considering to add capability to define custom attributes for issues and pull requests. It may be able to use for managing the status of issues.

[Paymanonline]

gitbucket-label-kanban-plugin is a good plugin but not enough.
Currently issues has only 2 state (Open, Closed).
I meant at least it has to have 4 state (New, Open, Resolved, Closed) like what Bitbucket has.
This way issues Workflow is more clear.

[takezoe]

My understanding is that gitbucket-label-kanban-plugin gives us the ability to use label as status.

If you want to have complex wokflow, using label or custom attributes and combining the status of open/closed with them (e.g. Done = closed) would work and be more flexible.

Though I'm not sure if we can do such thing in the current gitbucket-label-kanban-plugin, I prefer to leverage labels (or custom attributes) in order to keep GitBucket core simple and maximize the extensibility by plugins.

[takezoe]

Custom field support is in progress: #3034