It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×42,787
×6,076

question asked: Feb 05 '14, 8:36 a.m.
question was seen: 2,650 times
last updated: Feb 06 '14, 6:41 a.m.

Related questions

FAQ - How this Forum works

Can an attribute ID be arbitrarily picked ?

0
long TRUONG (365●4●118●146) | asked Feb 05 '14, 8:36 a.m.
edited Feb 05 '14, 8:38 a.m.
 Have noticed all OOTB attribute ID's come in a long string in the form of 
com.ibm.team.workitem.attribute.<attributeName>
like the ID of any other RTC entities.

But when creating new customized attributes, found that their ID can be arbitrarily picked, as long as there are no embedded blanks (and probably most of the special chars).

Is the long, descriptive ID built that way just to have an effective way to actually identify the owner/creator and the type of the entity, i.e. the <attributeName> is a workitem.attribute created by com.ibm.team ?
Is there any implication not to use the implied convention, or to use the convention, besides the creation or the avoidance of a confusion in trying to figure out what an entity is by name ?

Accepted answer

0
permanent link
Krzysztof Kaźmierczyk (7.4k●3●74●103) | answered Feb 06 '14, 3:44 a.m.
Hi Long,
There is no specific rule regarding that. I have found many repositories where admins just gave id without any prefix. Anyway, from my perspective it could be a good practice to use a convention like for Java packages - give creator name as a prefix to improve search experience when administering attributes.

Let us know if that helps.
long TRUONG selected this answer as the correct answer
Comments
sam detweiler commented Feb 06 '14, 4:44 a.m. | edited Feb 06 '14, 4:44 a.m.

we override and replace the generated id for custom items with our own

com.company.type

com.xx.workitem.attribute.type.xxx
com.xx.workitem.enumeration.literal.xxx

but thanks for asking.. your question makes me wonder if we have made a mistake on one area.  we assigned specific state ids to our custom defect workflow.

but if a workitem changes type, then the states won't map to the new workitem type ids.

you can change a workitem type very easily.

luckily we have only deployed one project on the new process template.

long TRUONG commented Feb 06 '14, 6:41 a.m.

 Thanks Krzysztof.


That was what we thought !

Your answer

Register or 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.