Package: taiga-stats
Taiga Stats - Your Taiga Statistics ToolThis is a script for all you Scrum||Kanban masters out there who use Taiga and are interested in visualizing progress and generate some automated statistics and graphs.Taigais an Open Source virtual Scrum and Kanban board that is popular for managing projects and work. We use a physical whiteboard at work but I mirror the status of stories in Taiga so that I can collect some statistics and generate diagrams and graphs using this tool I wrote.Features$taiga-stats--helpusage: taiga-stats [-h] [-v] [--url URL] [--auth-token AUTH_TOKEN]{config_template,list_projects,list_us_statuses,burnup,store_daily,points_sum,cfd,deps_dot_nodes,deps_dot}...Taiga statistic tool. Default values for many options can be set config file;see the command 'config_template'.positional arguments:{config_template,list_projects,list_us_statuses,burnup,store_daily,points_sum,cfd,deps_dot_nodes,deps_dot}Commands. Run $(taiga-stats <command> -h) for moreinfo about a command.config_template     Generate a template configuration file.list_projects       List all found project IDs and names on the serverthat you have access to read.list_us_statuses    List all the ID and names of User Story statuses.burnup              Print burn(up|down) statistics. Typically used forentering in an Excel sheet or such that plots aburnup.store_daily         Store the current state of a project on file so thatthe CFD command can generate a diagram with this data.points_sum          Print out the sum of points in User Story statuses.cfd                 Generate a Cumulative Flow Diagram from stored data.deps_dot_nodes      Print User Story nodes in .dot file format.deps_dot            Print US in .dot file format with dependencies too!Create a custom attribute for User Stories named'Depends On' by going to Settings>Attributes>CustomFields. Then go to a User Story and put in a commaseparated list of stories that this story depends one.g. '#123,#456'.optional arguments:-h, --help            show this help message and exit-v, --version         show program's version number and exit--url URL             URL to Taiga server.--auth-token AUTH_TOKENAuthentication token. Instructions on how to get oneis found athttps://docs.taiga.io/api.html#_authenticationSupport: please go to https://github.com/erikw/taiga-stats/issuesTerminologyUS- User StoryCFD- Cumulative Flow DiagramCumulative Flow DiagramFrom aCFDa lot of interesting insights about your team's progresscan be found. However I'm not found of repetitive work like counting and entering numbers in an Excel sheet. This had to be automated! Therefore I deiced to write this script to save data on a daily basis with a cron job and a function for generating this diagram. This diagram can the be put on a TV visible in the hallways.This is an example diagram generated frommock data:Textual annotations can be put in the plot by manually editing the.dat file.Also a target date for the project deadline can be specified. Then a line will be drawn showing the ideal work pace towards this date, as seen below where the target finish date is in week 46.To save the data and generate the diagram each working day I have this cronjob:$crontab-l|greptaiga0 18 * * 1-5            $HOME/bin/taiga-stats-cron.shand the scripttaiga-stats-cron.sh:#!/usr/bin/env shtaiga-statsstore_daily--tagsome_feature_tag
taiga-statscfd--tagsome_feature_tagUser Story Dependency GraphSome stories requires other to be completed before they can be started. I thought it would be handy if you could keep track of these dependencies in Taiga but simply writing for each US a list of other stories that this story depends on. Then from this information a.dot filecan be generated that should how you user stories depends on each other. This graph is very useful for work planning i.e. what to start with and how much parallelization is possible and at what stages.The stories that are marked as Done in Taiga have a green color in the graph.How to set up the dependency featureFirst create a new custom filed in taiga namedDepends Onunder Settings > Attributes > Custom Fields:Then go to your User Stories and enter some dependencies as demonstrated below.Then run the script and generate a PNG file.$taiga-statsdeps_dot$dot-Tpng-o./dependencies.png./dependencies.dotSetupInstallationMake sure to use a supported python version. See the keypythonin the sectiontool.poetry.dependenciesatpyproject.toml.$pipinstalltaiga-stats$taiga-stats-hIf you usepipxto install, you must specify a supported and locally available python version like:$pipxinstall--pythonpython3.9taiga-statsTo use this tool, you need to supply--urlto your taiga server e.g.https://api.taiga.io/--auth-tokenthat you need to obtain according to theofficial instructions.It's recommended to put these 2 values in the below describedtaiga-stats.conffile for easier usage of this tool!Config fileIt is tedious to have to specify the server URL and the authentication token every time. Also you typically work with some project at a time and would like to have default values for the project to use and maybe which tag to filter on. You can generate a configuration file to set these default values.$taiga-statsconfig_template$mv./taiga.conf.template~/.taiga-stats.conf$vi~/.taiga-stats.confDevelopmentMake sure to$ poetry shellbefore using tools like pyright LSP, so that it can find the installed dependency modulesReference for how to structure a python project:https://realpython.com/pypi-publish-python-package/Setup from GitClone this git$gitclonehttps://github.com/erikw/taiga-stats.git&&cd$(basename"$_".git)Install Poetry$pipinstallpoetryNumpy install issues as of 2021-10-31$ poetry installdid not work with Numpy on macOS. Solution fromhttps://github.com/python-poetry/poetry/issues/3196#issuecomment-769753478$pyenvlocal3.9.7$poetryenvuse3.9.7$poetryconfigexperimental.new-installerfalse$poetryinstallInstall project dependencies$poetryinstallNow taiga-stats should work!$poetryruntaiga-stats-h$# or$bin/taiga-stats.shTo install locally:$poetrybuild$pipinstalldist/taiga_stats-*.whlDevelopmentDocumentation generation$poetryrunmkdocsserve$poetryrunmkdocsbuildbutbin/gen_docs.shwill take care of all that plus more!Releasing$bin/gen_docs.sh$viCHANGELOG.md$poetryversionminor&&ver="v$(poetryversion-s)"$gitcommit-am"Bump version to$ver"&&gittag$ver&&gitpush--atomicoriginmain$ver$poetrypublish--build