Jburns,

I've attempted setting the Default Literal and the Unassigned Literal to the same value, but when I create a new defect (the work item that has the field for which I'm applying this enumeration), this field does not have to be reset in order to save. In addition, defects that have been updated with this attribute change also don't need to have this field reset in order to save other changes. It seems we're still in the same predicament - is there any additional guidance you can provide?

Thanks!

With RTC 3.0x and higher, it has become a mandatory requirement to assign a default literal value.


is there a way around this ? It negates the ability to set an enumeration as mandatory on a specific state or state change as the "default" is already set and therefore populated.

Did I miss something ?

If you want the user to have to choose some value other than what is initially selected in the editor, you should set the Unassigned Literal to be the same as your Default Value.

This value will then be selected by default, but the attribute will still be considered unset.

Hope that helps,
- Jared

I just got pinged about this question and saw this response for the first time. The final part of the puzzle is that you need to configure a precondition on Work Item Save that requires the attribute to be set.

I was the "pinger" and the combination of Default Literal = Unassigned, plus the "Required Attributes" precondition got me exactly what I want - a non-meaningful default that comes up when the workitem is created that the submitter then needs to change before saving.