Real bizarre one here. I added Microsoft.VSTS.Common.Priority to a custom WIT (Process Editor) and assigned a DEFAULT rule with a VALUE of "99".
My product owner wants to prioritize the work items, with most defaulting to 99.
If I edit an existing item's Priority (this NOT BacklogPriority) and save the item it shows correctly in the query results, but if I click on that row (or any row above it???? Strange!!!!) it reverts to 99! If I edit the item by double-clicking it, it reverts to 99. BUT! In the history I see my edit, going to the new value. Also, if I edit the item in VS2013 it shows 99, not the new value. BUT! If the tooltip on the label shows that I last edited it FROM 99.
If I create a new work item I don't have this problem - it seems to be only existing items. I believe these items were imported via Excel. I was wondering if there could be mismatched value assignments between the relational DB and the cube (which I don't think is used), so I changed the reporting type of this field to "detail". That didn't seem to help. Either the 99 being displayed is the original assignment or the default value. Since I can't reproduce this with existing items I don't know where it's coming from. Also, if I edit the item while it's showing the old value and save it, the value is changed to that old assignment and is reflected in the history.
Is there a db maintenance task I can ask our admins to run that might help? Any other ideas?
Thank you.