Among the structuring features to consider is a proper way to configure preferences.
Ideally, a list of settings could be edited and applied on the fly.
A simple one : I’d like to easily set the default language to french for every user and every project.
More advanced conf :
change the labels (currently, home page has this incorrect label : “Créé ton premier projet” and I want to replace “user story” with “task” out of pity for my confused non-technical colleagues)
change paddings/margins (taiga has trouble displaying accents properly)
disable features and hide the corresponding buttons depending on roles, like creating a workspace or a project
It could also benefit you, since giving administrators more control would free you to work on other things and let them configure what they need.
Being able to do that without restarting the server would be a game changer, as it would be deployed for a pretty large entity, with many simultaneous users. I’m willing to help with the implementation of the feature if needed.
We will probably provide a way to configure default project template and such for a given workspace, the groundworks has been thought for that purpose. For things like defaults statuses, kanbans, etc
About configuration instance-wide, we try to provide as much flexibility as we can through env vars and django configuration file (changes of which require a restart).
Default language code could very easily be added as a configuration option, we will look into it. We also might add a language choice option for user directly on subscription.
About the labels: thanks, we will fix the typo. In time, we would like to set up a collaborative translation platform, this way anyone could add a new language and fix translations mistakes.
Giving a way to change vocabulary might be difficult since it could cause confusion with future feature or documentation we will provide for the tools or with support services. For example, “task” will probably be an object that will also exist in Tenzu later-on so if story was already renamed to task… But we are still thinking about the term “story”, exactly because we also want to take care of your confused colleagues
change paddings/margins: We try to make the software as inclusive as possible, so don’t hesitate to alert us in case of display error (well, excluding mobile display since Tenzu is not responsive at all yet ^^’). We will eventually provide a way for a user with vision trouble to dynamically adjust their preference (make text bigger, etc), we have built Tenzu using design token for that very purpose.
disable features and hide the corresponding buttons depending on roles: That’s already the case, the interface adapt dynamically to the set of permissions possessed by a user :D
Thanks once again, I hope to have addressed everything, don’t hesitate if you have more insights :)
I have just checked, and the default language for an instance of Tenzu can in fact already be changed :) You can chose French by default with the following env var:
TENZU_LANGUAGE_CODE="fr-FR"
We’ll look into adding the language choice in the subscription form.
Tenzu’s current structure of Workspaces → Projects → Swimlanes → Tasks is excellent for organizing workflows. However, different organizations often use their own terminology to match internal processes. For instance, in our organization, we refer to Workspaces as Desks, Projects as Assignments, Kanban boards as Stages, and Stories as Tasks.
It would be extremely helpful if Tenzu allowed users to rename these core labels via the configuration file or settings panel. This flexibility would make the platform more intuitive and adaptable to varied organizational structures and terminology, enhancing user adoption and customization without altering the underlying functionality.
Language option on subscription has been added and can be tried on our demo ;)
We’ll keep in mind the idea to provide a way to personalise the labels but it might be difficult. For now, the most obvious way I can see to do this is, on self-hosted instances, to overwrite the provided translation files. But we won’t be able to help much on this as this will not be an official workaround.
