Selecting kanban tags and project status tags

[nickbe]

Best thing would be to have 2 status configurations in a project.

1. Status fields for current project. (select project statuses from all the statuses configured)
2. Select kanban status fields for this project from the selected project statuses.

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?

[satrun77]

I'm not sure what you mean.

[nickbe]

Select the projects status tags from all the status tags first. (Different projects might require different status tags)

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. The kanban should always show up in the same order.

[nickbe]

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

[nickbe]

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?

[satrun77]

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:

• Administration setting to define default tags that would be auto selected on creating a new project.
• On creating a new project you can select which tags available with field to search for a tag and select to add to a field. Then we only show the selected tags.
• the above feature to select which of these selected tags can be used in Kanban.

[nickbe]

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'. Then the user can create different tag groups and below each group are the current tags. (Exactly like he is now). And when creating a project you just select the 'tag group'.

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)