-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Selecting kanban tags and project status tags #83
Comments
I'm not sure what you mean. |
Select the projects status tags from all the status tags first. Then select the kanban tags from the projects status tags. The reorder function should then be done with the project statuses instead of the kanban statuses. |
Use tristate buttons to select the status tags per project and at the same time the status tags that should be visible in the kanban. See attached image. First click enables the status (exactly like now) and the second click adds the kanban view for this status. Third click again deselects the status tag. This would also resolve #93 |
back from my holiday I was wondering if it would make things easier if we define tags not globally but per project. pro would be that if you manage lots of different projects types the all the different tags would be easier to manage. A disadvantage would be be that you have to define all your tags from scratch for each project. (until there's also some default tags) What do you think about this idea? Nonsense or worth thinking about? |
Currently you manage the tags from an admin interface, and then they are all displayed in the project form and issue form. The request here is valid and I agree on. Not all projects will have the same workflow and tags. Tags per projects, means I will have to re-implement many of the existing functionalities. (Longer time to complete the job). Option:
|
Thanks for your thoughts on this. I was just thinking about another all together different approach: The current tag system is easy and I like it to keep a central admin setting for them. But what if we invent 'tag groups' in the settings: First you create/select the tag group - let's assume the initial group is simply called 'default'. This would work a little bit like a template system, but might be much easier to work with (and probably a little bit easier to implement) |
Best thing would be to have 2 status configurations in a project.
I suggest two seperate rows of statuses. Each time I enable/disable status for the current project a second kanban tag becomes visible and is avaiable for being selected.
What do you think?
The text was updated successfully, but these errors were encountered: