A value provider you configured on the attribute has filtered out the chosen value.
We have an enumeration called that is used for the attribute TargetRelease and we have a value that is Archived (in 4.0.0.1). We have a small subset of work items that still have the archived value, which displays just fine.
This morning, in advance of adding a validator for a totally different attribute, I enabled "Attribute Validation". Since I didn't have any validators used by any of the work items, I didn't think it would be an issue.
I have 2 people now who report getting that error when attempting to add a comment and save on a work item with that archived enumeration value. (confirmed multiple clients including web client)
Is this expected? I thought archiving an enumeration value would be fine for existing work items but just wouldn't be shown when attempting to set the value. Or is this a bug? Is there any way around this (other than un-archiving the release or not having attribute validation?
Susan
2 answers
and
so the archived values for the enumeration wouldn't qualify for a valid value for the attribute anymore.
So, I feel this is expected. please feel free to correct me if got the requirement wrong.
Comments
Morning,
Almost 3 years... but i have the same issue.
I've solved it with a Validation Script that always returns "OK" linked to the enumeration.
Hope it can help someone else that have searched for a solution to the same error.
Something like this:
dojo.provide("org.ibm.team.workitem.validatorAlwaysTrue");
dojo.require("com.ibm.team.workitem.api.common.Status");
(function() {
var Status = com.ibm.team.workitem.api.common.Status;
var val = dojo.declare("org.ibm.team.workitem.validatorAlwaysTrue", null, {
validate: function(attributeId, workItem, configuration) {
try
{
return Status.OK_STATUS;
}
catch(err)
{
console.log(err.message);
}
}
});
})()