Why are archived values in enumerations taken as Invalid by attribute validation?
I have a custom enumeration for our product release and once we complete a release, the "code name" for that release is archived (since it is only used prior to shipment). We also have Attribute Validation enabled.
Once this is archived, RTC seems to take it as an invalid attribute value, even when someone attempts to add a comment to the work item. We want it removed from the drop-down so that people cannot select it to change it to that release codename, but it should still be considered okay to be *in* an existing work item. Is there any way to get this working? Susan |
One answer
fun eh? you can only do this today with database hosted enums.. Process config based enums must continue to be defined forever for the rest of the system to work.
|
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.