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
We should write down our workflow on how we handle feature requests and bugs at organization level.
As we already discussed, we want to use Github projects because we can use them across all repositories.
My suggestion would be that we create ALL feature requests and bugs in this repository. After we prioritized them, we create an Epic issue for feature requests where we can have technical discussions and list all subtasks. Every issue should be added to a global project where we create different views. For our release cycles, we could use milestones.
The text was updated successfully, but these errors were encountered:
When planing to implement a feature, we create an issue, called "Epic", collecting everything about the feature. This issue shall be labeled type:epic and contain a description, any related information, as well as acceptance criteria / definition of done.
For implementation, we break down the epic into implementation issues which are linked to the epic. An implementation issue is a vertically integrated, small subscope of the feature defined in the epic.
We should write down our workflow on how we handle feature requests and bugs at organization level.
As we already discussed, we want to use Github projects because we can use them across all repositories.
My suggestion would be that we create ALL feature requests and bugs in this repository. After we prioritized them, we create an Epic issue for feature requests where we can have technical discussions and list all subtasks. Every issue should be added to a global project where we create different views. For our release cycles, we could use milestones.
The text was updated successfully, but these errors were encountered: