It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,856
×11,987

question asked: Jan 29 '14, 10:41 a.m.
question was seen: 3,222 times
last updated: Jan 29 '14, 10:41 a.m.

Related questions

using Delta-config for custom enums per project, help, literal name best practices

0
sam detweiler (12.5k●6●195●201) | asked Jan 29 '14, 10:41 a.m.
 We are successfully configured to provide a custom enum for each dev project using shared project areas and the delta-config support introduced in 4.0.1.

our process is to name the field

com.xx.workitem.enumeration.literal.L1.... L2... etc

butI think this will cause a problem in reporting across teams..  as EACH will have an L1, L2...
but the text will be different and mean different things to them.. 

should the name be 
com.xx.workitem.enumeration.Projectname.literal.L1.

if they ever copy to another project area (unlikely) we are gonna have mapping problems regardless..

Be the first one to answer this question!

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.