There seems to be limit of 8 on the number of kanbans per project. Also a limit of 12 stories per column. How can we modify the same?
Yes, there is a limit of 8 kanban for now. It’s a bit arbitrary since we didn’t make the UI able to display an unlimited number of kanban, nor do we have the feature to change it dynamically yet. If you deploy Tenzu yourself, you can change that number using TENZU_MAX_NUM_WORKFLOWS env var. On our demo I’m afraid that number can’t be changed.
What do you think would be a good number? Do you have a use case where you need more than 8 for a single project?
About the story limit, could you tell me more? We don’t have any limit set on the number of stories (we test Tenzu with a sample project with more than 2000 of them), so you shouldn’t be restricted on creating away as many as you want to!
Hi and have a wonderful day.
I work on many volunteer projects and “need” a different number of workflows.
In one project, I manage a farm where we offer seminars for free to others. There, we use communal meals (for the people who live there) to reduce costs. To manage such seminars (which tasks have been completed, which have not), plan the meals, organize the groups, coordinate advertising, and many other tasks, we would need about 10 to 15 workflows.
I am also responsible for IT, which would be one of the subgroups/workflows.
My idea is that everyone can choose how many they can handle, but there would be a limit for you, so it doesn’t get out of hand on your test servers. By default, I would still set the limit to infinity.
Thanks @kal for your use case, we’re taking note that you would get a use of the max number of kanban in a single project being increased.
We can’t do infinity for now because of UI concerns, but you can chose the number that you want on any self-hosted instance.
In time, we will think about making this number more easily dynamic and about what that would mean.
Hi Jrymer, there are two env files (“.env” and “tenzu.env”) which file do we add the TENZU_MAX_NUM_WORKFLOWS=15 to?
Hello @Atul , if you are talking about the production deployment recipe we are providing, the .env file contains only variables used by the docker-compose so you probably don’t want to change it unless you want to pin the version of Tenzu that you are deploying.
All the application variables you want to set for the backend need to be put inside tenzu.env.
We tried to explain the use of every configuration files in the docs.