Home | Applications | Documentation | Transport | Personal |

Documentation

Home | Cloud | C# | Database | DevOps | Revision | Web |

DevOps | Repos | Pipelines | Boards |

Boards (Projects)

Introduction

Control of developments in the modern world use Kanban Boards. The are in DevOps as well as other software like Teams. This page is mainly about usage and navigaton.

GitHub Projects

GitHub Projects are like DevOps Boards.
When you add a new project, you are asked what type. Normal Kanban boards or Automated Kanban boards.
You will then need to add Cards. The project has 3 columns, To Do, In Progress and Done. You can add assignees and tags such as 'Bug'.
To add a Card...
In ToDo, add a note
Click on '...' and convert to issue
Change the Assignee, Type (Bug, Enhancement) and Milestone for amount of work required
Very basic. You can add columns, move the columns, move issues to cloumns and move the issues within the columns for ordering the issues.
The filtering is very basic. The type can be selected, but the value of the type has to be typed in correctly, without options, and the list only appears when you have finished typing the value and pressed enter.

DevOps Boards

DevOps boards are like GitHub Projects.
Boards shows 3 columns, To Do, Doing and Done. There is an option in the To Do column to add an item. This allows you to add a note as in GitHub Projects. Once you save, you can then open it up and set the assignee and the effort (but it doesn't say what 1.5 means). Has deployment/branches as Project.
The sprints and the filters are excellent. There is also a 'work remaining' field.

Conclusion

DevOps is a much better and more refined product. Use GitHub as a repository but DevOps for task management.