We dedicated one Le lab session to this project:
Get it while it is hot!
At TailorDev, we work seven effective hours a day and Watson is
very useful when it is time to send invoices. Time to time, we use the output of
watson report to inform our clients about their projects (cheap yet
comprehensive progress report). Nonetheless, it does not feel natural to do that
and we also have to do the maths when we all work with the same client.
Crick does not change the way Watson works or how you use it but it adds a few interesting features. First, synchronizing your Watson data (called frames, projects and tags) allows to backup them. Next, the web interface allows to quickly browse your data and help you answer questions such as “how long did it take to setup CI/CD on that Java project”. Last but not least, you can create “teams”, i.e. sets of members and projects, and create reports for them too!
We are not sure about this term “team” yet because we do not have a unique TailorDev team for instance, but rather a team per client. That way, there is no need to force Watson users to change their habits, like respecting a specific project name or any other convention. Instead, add members to a team and ask them for their own local project names (Watson uses project names as unique identifiers).
Example: you have a
Project Xfor client
Xand two employees
Ahas logged time under
x. By creating a team with members
Band project names
x, you will get a report for the entire project.
You get more accurate reports that are automatically updated, and you can create as many reports as you want. Errr… I meant as many teams as you want
As mentioned previously, we designed Crick to enhance the Watson experience, but we did not want to change Watson. In an upcoming iteration, we will probably add a read-only overview report for both projects and teams. Our motivation is to be able to share these reports with our clients to keep them informed at any time. We might also display GitHub/GitLab information on these pages.
Crick is released under the MIT License. If you are willing to contribute, be sure to read our contributing guidelines. We have a few easy pick tags for newcomers, and we are willing to mentor/help!
We would love to read your thoughts, such as things that did not work as expected or feature requests. Feel free to submit new issues.