Frequently Asked Questions
Frequently Asked Questions...
Frequently Asked Questions...
There are important considerations governing the Affero GPL license in use by Taiga. Please be sure you are familiar with your rights and obligations before starting to work on the Taiga code.
Since the open source license covering Taiga is AGPL, you can freely clone/fork the repo and make any modifications you want. Just remember the basic condition that the Affero GPL brings to the table: any Taiga instance must easily provide to all users a link to the source code that is running that particular Taiga service.
If you don’t make any changes to the code, the link is pretty simple, it’s just a link to Taiga’s github page. But if you intend to make adaptations or changes, you must provide a (de-facto) zero-cost way to obtain the complete modified source code. The easiest way would be to fork the repo on github and point your users to that forked repo (you can place that link in the documentation somewhere).
Our repo is quickly evolving so we suggest you keep careful track of our changes, that way you can easily benefit from our own improvements “for free”. Some users have decided to use our Taiga cloud instance together with our public API and only develop a separate integration layer that effectively lives outside the Taiga source code. By doing this you can “forget” about changes taking place at the Taiga source code.
Your needs will dictate which option suits you better.
Please read the AGPL 3.0 license covering Taiga.
If you would like to discuss specific dual-licensing with us, contact us a firstname.lastname@example.org.
Under Project SETTINGS, you have probably seen the Public/Private toggle button. Also, upon project creation you are asked about this.
Private projects are projects that are accessible only to project members. You still have the option to allow for other Taiga users or anonymous users (including search engines) to interact with the project if you allow for that using the External User role under SETTINGS > PERMISSIONS, but this is not enabled by default.
Public projects are projects that are forced to be at least viewable for non members and anonymous users (including search engines) through External user role. They also show up under Taiga’s DISCOVER page.
The configuration flexibility allows for some overlap. You decide what’s best for your project. Please note, Public Projects do not count for the paid plans on taiga.io, they are always free of charge regardless of team size or number of public projects.
Absolutely! Taiga supports several 3rd party tool migration processes. Jira, Trello, Asana and Github as well as other Taiga instances are supported. Be sure to check the documentation.
Sure! The Taiga community is awesome and helps us translate the Taiga user interface into more than 20 languages.
To see if your language is supported, simply go to EDIT PROFILE and pick your choice under Language drop down.
If the language is meant for Right-To-Left setup, it will also activate this mode.
Our text editor has support for Right-to-Left setup too, so you can combine both options as you please.
To know more about Taiga’s localisation efforts and language support, please visit our Weblate page.
There are many different ways to contribute to Taiga’s platform, from patches, to documentation and UI enhancements, just find the one that best fits with your skills. Check out our detailed contribution guide.
We are sorry to hear that. The most probable reason any project would be blocked is because the owner of that project did not subscribe in time to an appropriate paid plan. The project hasn’t been deleted at all, it is simply not accessible for the time being.
Taiga.io does not immediately block projects upon unsuccessful payment, it will continue to attempt the payment three more times during the subsequent 5 days after the first failed attempt. Taiga will also send an email for every unsuccessful payment attempt but the only recipient of those emails is the project owner.
If you are not the project’s owner, we suggest you contact them. Please tell them to follow the instructions on Taiga.io to subscribe to a paid plan. Your project will immediately be available again.
If you are the project owner and you receive one of such emails, proceed to change the debit/credit card details as an invalid or expired debit/credit card is number #1 reason for a failed payment. Updating the debit/credit card details with a valid one before the projects get blocked should automatically prevent the blocking process. If the projects are already blocked, entering valid debit/credit card details immediately restores the account status and allow projects to be accessible again. You can simply go to youruser settings subscription settings. If you encounter any problem simply contact email@example.com and we will give you instructions to follow so you can subscribe to a paid plan.
Scrum agile technique states that if an estimated user story is not finished, it can’t be counted towards a sprint’s user story points completion.
The rationale is simple, Scrum sprints care about finished work that can de properly validated during the Sprint’s Demo. Partial or unfinished work, while perfectly acknowledgeable, is not meant to change the progress metrics that are geared towards delivered value, not time spent.
This very binary approach frustrates some agile teams that prefer progress charts to represent any partial progress.
Some Taiga users have asked to be able to assign points to user stories tasks and keep track of them towards progress. This way, as an example, a user story could be 10 points split up in 2 tasks 5 points each. They would argue that a finished 5-point task could make the user story 50% finished towards sprint and burndown metrics even if the user story is not finished.
Product-wise, we continue to evaluate the risks of allowing partial or continuous progress metrics. For the moment, we strongly suggest you read Agile Antipattern: “All for sprint’s speed” in our blog. There are ways to address the underlying problem (and need) without the partial-progress approach.
Taiga is an Open Source platform. At the same time, we provide a freemium cloud/SaaS offer so you can use our own infrastructure to host all your projects and teams. Depending on your use, we may charge for this service.
But who has to actually pay?
A project owner that needs to go beyond the FREE PLAN needs to pay a monthly or yearly amount based on Taiga’s Pricing Policy. This project owner is responsible for the payment of all their projects' team members. Project owners only pay once per team member, regardless of how many projects those team members belong to or the overall number of private projects a project owner administers.
As a project owner, you can always check which Taiga users are counting towards your paid subscription under user settings subscription settings.
Regular team members, even if they enjoy the ADMIN role in a number of projects, do not pay. They are taken care of by their Taiga project owner.
Of course, a Taiga user could be a regular user under a paying Taiga project owner and, with that same Taiga account, be project owner to others. In that case, this Taiga user would pay for their respective projects' team members.
If you’re new to Taiga and would like to invite your team to the platform, you need to do so after you have created a project. Once you have created a project, you can go to SETTINGS>MEMBERS and add them. Invites will be sent by Taiga to all of them to join both Taiga and your project. If you invite team members that are already Taiga users, they will be immediately added to the project and they will get notified as well.
Inviting team members to Taiga requires inviting team members to at least one project where you have ADMIN or OWNER status, that is, you can access the SETTINGS panel for that project. Once they have a valid Taiga user, they can be invited to many other projects and they can use Taiga based on their account type.
Transferring the project ownership of a project is possible both ways; someone with Admin status requests the project ownership or some project owner invites a project ember to become the new project owner.
This is done by accessing the Request ownership / Transfer ownership option under SETTINGS > PROJECT DETAILS. It will trigger a request for confirmation to the other party, who can accept or decline the petition.
Since the difference between Project Owner and Admin status is just formal (both roles can do almost everything), you don’t need to transfer a project for any practical reasons. This action is usually linked to a project owner leaving the project or the company in which such project is managed. On tree.taiga.io, it is relevant for the billing information, since only project owners are considered potentially billable (depending on their account type).
Transferring the project ownership of a blocked project might be an unexpected burden to the transferee so we would like to avoid that at all costs. The simplest and fastest solution is to simply subscribe to the minimum paid plan on a monthly basis and then do the project ownership transfer normally (the other person would still have to accept clicking on an link sent to them via email).
On exceptional occasions we have an alternative plan that will take much longer, which is that both you and the transferee send an email to firstname.lastname@example.org explicitly requesting the project ownership transfer for one or more projects where both of you are already members. That will trigger a manual action on our side but you might have to wait a several days.
Taiga includes optional custom fields in its administration panel. It will provide teams with a flexible input to fit in their workflow.
Users with administration permissions will be able to create new custom fields for their project Epics, User Stories, Subtasks and Issues.
Simply go to your Project Admin section > Attributes > Custom fields and add, remove or edit any of those for your choice of Taiga entities.
You will then be able to see the new custom field option within the Epic, User story, Subtask or Issue view, depending on your choice.
Please note than custom fields cannot be used to filter Taiga items. We plan to add this capability in the future. However, both the API and the live CSV exports do contain the custom fields information.
The iocaine powder is a reference to the movie The princess Bride. It features a colorless, odorless, and deadly poison from Australia. Character Westley spent two years building up an immunity to iocaine powder. He uses it to trick Vizzini in their battle of wits.
The iocaine feature means that a user is out of their comfort zone. It could signal that a team member is learning a new ability required to close a task. It can also mean that this user is over-reaching or over-stretched.
Iocaine is not a bad thing.
We all recognize that reaching beyond our boundaries is a good and healthy thing albeit stressful and uncertain. The best way of taking risks is to be sure your team members are aware that you are doing so. They may be more inclined to forgive faults, be supportive, lend a hand, or be kind!
We use it internally, and we have learned to respect when people indicate they are taking an Iocaine dose!
When a user takes iocaine it will be shown in the tasks card as a small poison bottle, and your user picture will be tinted to a purple color.
When you see this in a taskboard task you will notice that a colleague (or yourself!) are out of their comfort zone and closing the task could use some help or a little bit more time.
The team member who is taking care of the poisoned item should be the one deciding if it’s iocained or not. For a team member a task could be trivial (without iocaine) and really difficult for another (a lot of iocaine).
Tough question. There is no consensus about time tracking in agile methodologies. Some people think agile methodologies are not meant to include time tracking, while some really need time tracking for a variety of different reasons. Either way, Taiga is built to accommodate multiple use cases.
But, of course, agile methodologies are meant to be malleable, so even if we decided to not implement time tracking as a feature in Taiga, teams are implementing it by using workarounds (like adding hours in the task or user story title, etc.)
To accomodate these practices we came out with something that could fit in any team workflow and solve many different problems: custom fields.
Thanks to Olegerm who developed this integration between Toggl and Taiga.io
Yes, you can cancel at any time. Taiga.io plans are paid monthly or yearly, so if you cancel, once you do so, the plan will run to the end of the period and not renew.
Check the detailed article with all the options to use markdown in the Taiga editor.