We have a custom field, whose default value was (TBD). For some reason, it decided to update the field to the default value at every opportunity, overwriting previous values with the default at transitions, edit, resolved. I removed the default value, and now it's inserting (None) instead of (TBD) still overwriting values. I created a new context with the same values, and the same behaviour continues.
I am preparing to delete the context, re-index, create a new context and associate it.
Has anyone else run into this type of behaviour, I'm more than a bit baffled. It's only happening on one project system wide, the other projects seem to be ok. Something must have gotten corrupted somewhere, but I have no idea where.
So it appears that creating a custom context is basically the same as creating a new field. In that database pointers get updated. The field was exhibiting this behaviour, I assume because with the context data updated, it assumed existing data in the fields was either bad or empty defaulting to (None) or (TBD) depending on the setting.
I searched by Project and the Custom Field, changing the field data (in this case teams) from the "old" value to the "new" (same) value.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
...attest to the experience of an urgent approval that gets lost in the boss’s inbox and requires that special “Please Approve” email or text message. In an age where we have distributed teams...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs