Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Tags vs. Attributes

We are using RRC client version 2.0.0.3.

Would you please give me an idea of when to use tags versus attributes? Are there any best practices on using them?

Thank you!

0 votes



2 answers

Permanent link
Tags are good for informal, temporary and overlapping grouping, typically when the scope is limited. For example:

daniel-current-working-set
UX-need-to-check
themes: usability, performance, security


Attributes, on the other hand ...
* Exist in all artifacts of the same type
* Have specific data types (string, enumeration, date, person, etc)
* Can be edited en mass in the project list artifacts view for a set of artifacts

For example, attributes are often used to represent state (draft, approved), target release, etc.

So you want to use attributes sparingly and put more thought into their data types and which enumerated values are appropriate.

You want to avoid, after a few years, having artifact types with large numbers attributes, most of them no longer used. Tags give you a way of doing the one-off groupings; attributes give you ways that are common and enduring.

0 votes


Permanent link
Thank you, Daniel, for your quick and thoughtful response!!!

0 votes

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: May 11 '11, 3:01 p.m.

Question was seen: 4,617 times

Last updated: May 11 '11, 3:01 p.m.

Confirmation Cancel Confirm