![]() I also enjoy the ability to order issues to represent priority as well as the quick filtering to know what’s assigned to who. What makes HuBoard usefull to me is mostly the board visualisation and the ability to use drag & drop to change a Github issue’s state. I confess that I don’t use a lot of the new features available. Once the ticket is in production and tested there, then and only then the ticket is closed. On Prod : The ticket has been deployed to production.Ready For Prod : The ticket has been tested on staging and works as expected.On Staging : The ticket is mostly completed and is currently tested on the staging environment.Going : Someone is currently working on it.Backlog : This needs to be done eventually.For instance you must be familiar with wording like “Going” or “Testing”.įor reference, here is what we use at Drivy, but obviously it needs to adapt to your own project: You get to add labels to your issues and these labels are used to define in which “state” they are. HuBoard uses the Github public API extensively to give you a better way to manage your workflow. In a sentence, HuBoard is a simple tool that acts as a layer on top of your Github issues. Knowing that, here’s how I decide to organize my issues with HuBoard. Personnaly I’m more a git flow kind of guy and I’m not always so confortable with my test suite that I can deploy directly to production. For instance you could follow the Github Flow and know that master can be deployed and features branches are being worked on. By not forcing a workflow it leaves you the opportunity to create your own way of doing things, adapted to your needs. However this limitation can be a good thing. I a team of more than a couple of people, it’s also difficult to know what needs to be deployed, what I currently being worked on etc. It is problematic because a more junior developer might end up loosing their mind in a clutter of issues. Personally I think that it’s both a good and a bad thing. There is one problem however: Github doesn’t provide a clear workflow like tools such as Pivotal.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |