Redmine

Ask - I just added a Custom Field (long text) and made it search-able. Seems to work reasonably well.

It would be better to have global,unified tagging feature so you could select one or more tags to your wiki page, document, forums or issues maybe even changesets.

This kind of tag information could be used to construct more spesific views that can group together all that information.

+1 for tags, is one stopper to migrate our system to redmine

+1

A true tagging system would be very handy.

+1 I think this would be a great feature. There are several tagging plugins for Rails already that we can use.

+1

+1 Would improve usability...

+1 like this idea very much!

+1

Add tagging support for projects as well. Being able to tag a project "opensource" versus "proprietary" along with other tags would be very useful.

So anyone have any plans to work on this? Otherwise I'll take a crack at it. It looks like some people want tagging all around the system, but I would probably limit it to tickets for the time being since that's all I really need, and leave it up to other people that want other features (besides I've never hacked around with the Redmine source so this will be my first foray into that ;))

+1!
Tags could substitute category. It's very web 2.0! ;)

How This Custom Field with the searchable option will be used as tag.I want this Tagging functionality in News,Issues,Documents,Forums,Wiki,Messages,Changesets

Custom fields can be created only for Projects,Issues and users as far as i Know

For Tagging Documents under Particular tagging is there any Plugin Avaiable

I want to implement This Tagging functionality in all possible places in Redmine.How can i accomplish this functionality.Please guide me in this issue

+1

+1

+1

I do not mind tags, but they will not be able to replace Categories.

Currently categories have default assignee. This means: create issue, drop it to a category, and issue gets auto assigned. With tags you will not be able to resolve who is auto assigned to issue. And assigning multiple people only makes everyone think that 'the other guy will do it'.

Tags yes, but do not remove Category, unless someone has a solution on auto assign an assignee from tags?

This is related to #480 - "Wiki: Support categories tagging and autolisting" and the more general issue #2897 - "Tagging in Redmine".

Personally tagging would be good for the wiki as pages don't always fit into a neat category so being able to add tags is one step better than just relying on the good search facilities in Redmine.

+1

+1

+1

+1

+1
I really miss this feature. For my needs, it could replace category in tickets.

+1 from me too.

+1

+1

The possibility of tagging issues is a minimun to identify areas affected by them.
Ok, it is not like the more desirable feature of mapping issues with the configuration items affected but as currently there is no pluging providing an inventory or Configuration Management DataBase I think that tagging is an interesting first step and more than enough for most of us.

I agree that tagging is not a substitute for categories.

+1

+1 (I'll also check if there's a "vote" feature in redmine :) )

We don't use redmine yet and I thought that the categories are actually the tags, but further investigation reveals that is not. Sad. It won't take much time to anybody who knows ruby to ad one more enum field like categories and add possibility to search issues by that field.

Of cause it must be possible to add multiple tags.

+1

+1

http://github.com/mbleigh/acts-as-taggable-on

is a very active plugin, and easy to setup ;)

+1

+1

+1 ... this would a major step towards completely, truly ruling the world.

Tags are nice but I find them to get really disorganized due to users putting in either random or excessive amounts of words, which is why I favor admin/manager controlled categories they can select from.

You could always go the way of GMail and allow issues to be assigned multiple categories, instead of creating an entirely separate feature that does more or less the same thing (in my opinion).

I've just completed a prototype with this for a client using acts-as-taggable-on. Once I get their permission, I'm going to try to extract it into a plugin or core patch.

Mike K: Tags can become disorganized but I find that's better than having to define one Category per issue. I'm thinking about adding some permissions for editing tags, so you can restrict who can re-tag an issue (e.g. UserA can add new tags, UserB can only add existing tags).

Eric Davis wrote:

permissions for editing tags, so you can restrict who can re-tag an issue (e.g. UserA can add new tags, UserB can only add existing tags).
I like that idea and solves my only concern ;)

Letting privileged users manage (add/edit/delete) the tags via some sort of panel would be needed if you plan to replace categories though, especially for newly created projects so you can define new tags they can use without being forced to add new issues in order to do so.

Eric Davis wrote:

I've just completed a prototype with this for a client using acts-as-taggable-on. Once I get their permission, I'm going to try to extract it into a plugin or core patch.

Mike K: Tags can become disorganized but I find that's better than having to define one Category per issue. I'm thinking about adding some permissions for editing tags, so you can restrict who can re-tag an issue (e.g. UserA can add new tags, UserB can only add existing tags).

Eric,

Great to hear! The permission model you laid out seems like it will work well too. Might you also want to have a permission which allows the user to assign or unassign tags to the issue? That way, you can have a user (in my case a customer) who can not edit the issue but can tag it with existing tags. That way, they can affect "state" change without really being able to edit the issue. If you did it this way, it seems like the two permissions are:

• manage tags
• assign/unassign tags to issues

Will you be able to share tags across projects?

Mike K wrote:

Letting privileged users manage (add/edit/delete) the tags via some sort of panel would be needed if you plan to replace categories though, especially for newly created projects so you can define new tags they can use without being forced to add new issues in order to do so.

I don't want to replace categories yet, just add tags as a more flexible option. Maybe later we can merge categories and tags.

Randy Syring wrote:

Great to hear! The permission model you laid out seems like it will work well too. Might you also want to have a permission which allows the user to assign or unassign tags to the issue? That way, you can have a user (in my case a customer) who can not edit the issue but can tag it with existing tags. That way, they can affect "state" change without really being able to edit the issue.

I was thinking:

• view tags
• add new tag - e.g. adding a new tag
• manage tags on issue - e.g. editing tags on an issue, would only use existing tags

Will you be able to share tags across projects?

Yes, I'd think that would be needed.

I know it's a different subject, but I think tags should be employed more widely in redmine. It would be useful for documents as well.
Thanks

Eric Davis wrote:

Maybe later we can merge categories and tags.

IMHO it's better to keep both, categories and tags. Or, for example rename "categories" with "components".

Is there any progress on this issue?
Eric, I would like to offer my help, if you need some hands more :))

+1

Eric, are there any news?

Could this feature make ti v1.0.0?

Philippe Lafoucrière wrote:

I know it's a different subject, but I think tags should be employed more widely in redmine. It would be useful for documents as well. Thanks

I agree,
tags would be great for issues, but they are a must for documents