You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GitKraken provides various amounts of automating a project board. Currently when closing an issue I have to manually move the issue to the "Done" board.
Proposals
Issue movement
Imagine you are having a kanban board (backlog, todo, wip, review, done) then the following options would make total sense
Per default an issue is placed into Backlog
As soon as it has a description or an assignee the issue gets moved to ToDo
When a proper branch is created (maybe add a button to create and link a branch from the issue page) the issue gets moved to WIP
After creating a PR for the linked branch the issue gets moved to Review (as long as the PR is not marked as WIP)
After the PR is merged the issue gets moved to done.
Labeling
GitKraken also provides the feature to manually configure each board with a Scratch like event/action system. E.g. one is able to automatically add/remove a label to/from an issue: When entering the "WIP" board the issue receives the "Status: Work in Progress" label. After moving out from the board the label gets removed.
Screenshots
No response
The text was updated successfully, but these errors were encountered:
Feature Description
Introduction
GitKraken provides various amounts of automating a project board. Currently when closing an issue I have to manually move the issue to the "Done" board.
Proposals
Issue movement
Imagine you are having a kanban board (backlog, todo, wip, review, done) then the following options would make total sense
Labeling
GitKraken also provides the feature to manually configure each board with a Scratch like event/action system. E.g. one is able to automatically add/remove a label to/from an issue: When entering the "WIP" board the issue receives the "Status: Work in Progress" label. After moving out from the board the label gets removed.
Screenshots
No response
The text was updated successfully, but these errors were encountered: