What is Taiga?

On the first view Taiga (taiga.io) is a open source Trello replacement. On the second it is way more than that. Taiga does offer a lot more integration into Scrum and Kanban Workflow than Trello could ever do (even if you would pay for all those neat power-ups). Taiga is offered as hosted and self-hosted (as it is completely open source) and does offer all features in payed and free accounts on the hosted solution. Unlike tools like Gitlab where there are premium features that are held back for the enterprise offering this tool is developed in the open (https://github.com/taigaio).

Taiga does offer proper Backlogs and Sprints that are connected with each other. In Trello you loose the connection between your Backlog and Sprintboard at some point and tracking does get harder.

On top of that Taiga offers importers for Trello, Github Issues, Jira and Asana. These would be very helpful for teams to migrate away from current tools and organize everything in one place that was developed with Scrum and Kanban in mind.

Why do we need a Bugzilla Sync?

Automatic downsyncing of Bugzilla Bugs into Taiga would ease the job of POs, TPMs and SMs. You won't have to enter Bugzilla bugs in your teams Scrum Board anymore as you do now in Trello. To make it easier, it would be a good idea to support downsyncing first as this doesn't harm the Bugzilla database.

How could it work?

A user creates a custom search query on Bugzilla which results in a list of bugs that are relevant for the Backlog of the Scrum Team. This list will be checked against the current backlog and updated in Taiga (minimum including the title, bug number, bug description and severity). It should also check against current sprints to make sure that it is not added as a duplicate to the backlog.

Taiga does offer some APIs to achieve that. On Bugzilla side I am not sure, but as a last resort we could use a site crawler (EDIT:There is an API for Bugzilla: https://github.com/dmacvicar/bicho).

Looking for hackers with the skills:

python angular angularjs angular.js django taiga bugzilla

This project is part of:

Hack Week 17

Activity

  • over 7 years ago: okurz liked this project.
  • over 7 years ago: aspiers liked this project.
  • over 7 years ago: suntorytimed left this project.
  • over 7 years ago: suntorytimed liked this project.
  • over 7 years ago: suntorytimed added keyword "taiga" to this project.
  • over 7 years ago: suntorytimed added keyword "bugzilla" to this project.
  • over 7 years ago: suntorytimed added keyword "python" to this project.
  • over 7 years ago: suntorytimed added keyword "angular" to this project.
  • over 7 years ago: suntorytimed added keyword "angularjs" to this project.
  • over 7 years ago: suntorytimed added keyword "angular.js" to this project.
  • over 7 years ago: suntorytimed added keyword "django" to this project.
  • over 7 years ago: suntorytimed started this project.
  • over 7 years ago: suntorytimed originated this project.

  • Comments

    • vitoravelino
      over 7 years ago by vitoravelino | Reply

      I had a similar idea but for trello and a deeper sync (comments and status changes). I still need to think how it would work.

    • suntorytimed
      over 7 years ago by suntorytimed | Reply

      There is an API for Bugzilla: https://github.com/dmacvicar/bicho

    Similar Projects

    Improve chore and screen time doc generator script `wochenplaner` by gniebler

    Description

    I wrote a little Python script to generate PDF docs, which can be used to track daily chore completion and screen time usage for several people, with one page per person/week.

    I named this script wochenplaner and have been using it for a few months now.

    It needs some improvements and adjustments in how the screen time should be tracked and how chores are displayed.

    Goals

    • Fix chore field separation lines
    • Change screen time tracking logic from "global" (week-long) to daily subtraction and weekly addition of remainders (more intuitive than current "weekly time budget method)
    • Add logic to fill in chore fields/lines, ideally with pictures, falling back to text.

    Resources

    tbd (Gitlab repo)


    Improve/rework household chore tracker `chorazon` by gniebler

    Description

    I wrote a household chore tracker named chorazon, which is meant to be deployed as a web application in the household's local network.

    It features the ability to set up different (so far only weekly) schedules per task and per person, where tasks may span several days.

    There are "tokens", which can be collected by users. Tasks can (and usually will) have rewards configured where they yield a certain amount of tokens. The idea is that they can later be redeemed for (surprise) gifts, but this is not implemented yet. (So right now one needs to edit the DB manually to subtract tokens when they're redeemed.)

    Days are not rolled over automatically, to allow for task completion control.

    We used it in my household for several months, with mixed success. There are many limitations in the system that would warrant a revisit.

    It's written using the Pyramid Python framework with URL traversal, ZODB as the data store and Web Components for the frontend.

    Goals

    • Add admin screens for users, tasks and schedules
    • Add models, pages etc. to allow redeeming tokens for gifts/surprises
    • …?

    Resources

    tbd (Gitlab repo)


    Enhance git-sha-verify: A tool to checkout validated git hashes by gpathak

    Description

    git-sha-verify is a simple shell utility to verify and checkout trusted git commits signed using GPG key. This tool helps ensure that only authorized or validated commit hashes are checked out from a git repository, supporting better code integrity and security within the workflow.

    Supports:

    • Verifying commit authenticity signed using gpg key
    • Checking out trusted commits

    Ideal for teams and projects where the integrity of git history is crucial.

    Goals

    A minimal python code of the shell script exists as a pull request.

    The goal of this hackweek is to:

    • Add more unit tests
    • Make the python code modular
    • Add code coverage if possible

    Resources


    Bring to Cockpit + System Roles capabilities from YAST by miguelpc

    Bring to Cockpit + System Roles features from YAST

    Cockpit and System Roles have been added to SLES 16 There are several capabilities in YAST that are not yet present in Cockpit and System Roles We will follow the principle of "automate first, UI later" being System Roles the automation component and Cockpit the UI one.

    Goals

    The idea is to implement service configuration in System Roles and then add an UI to manage these in Cockpit. For some capabilities it will be required to have an specific Cockpit Module as they will interact with a reasource already configured.

    Resources

    A plan on capabilities missing and suggested implementation is available here: https://docs.google.com/spreadsheets/d/1ZhX-Ip9MKJNeKSYV3bSZG4Qc5giuY7XSV0U61Ecu9lo/edit

    Linux System Roles: https://linux-system-roles.github.io/


    Update M2Crypto by mcepl

    There are couple of projects I work on, which need my attention and putting them to shape:

    Goal for this Hackweek

    • Put M2Crypto into better shape (most issues closed, all pull requests processed)
    • More fun to learn jujutsu
    • Play more with Gemini, how much it help (or not).
    • Perhaps, also (just slightly related), help to fix vis to work with LuaJIT, particularly to make vis-lspc working.


    Bugzilla goes AI - Phase 1 by nwalter

    Description

    This project, Bugzilla goes AI, aims to boost developer productivity by creating an autonomous AI bug agent during Hackweek. The primary goal is to reduce the time employees spend triaging bugs by integrating Ollama to summarize issues, recommend next steps, and push focused daily reports to a Web Interface.

    Goals

    To reduce employee time spent on Bugzilla by implementing an AI tool that triages and summarizes bug reports, providing actionable recommendations to the team via Web Interface.

    Project Charter

    https://docs.google.com/document/d/1HbAvgrg8T3pd1FIx74nEfCObCljpO77zz5In_Jpw4as/edit?usp=sharing## Description