Adding new field to Iteration item

[Lukasz Socha]

Hi, 

I want to add new text field having name "explanation" into the iteration item in Rally. However, when I do that I receive the error:

"The Field could not be saved. Please correct the errors identified below and click one of the "Save" buttons."

Not sure what is wrong as I do not receive any error information except this above. Additionally I see the information message: "Edits you make to the name affect all projects in the workspace that are showing this field." 

I am the workspace admin and I try to create new field in one of the project including its child projects. However, I also tried to create new field on the workspace level but does not work as well. 

Do you know what can be wrong and whether it is possible to add at all a new text field into iteration item?

Best regards
Lukasz

[David LeDeaux]

Hi Lukasz,

On the screen where you get the error can you

1. Right click 
2. Click View Page Source
3. Search for: error

If there's a line found, paste that line here

[Lukasz Socha]

Hi David, 

Thank you for replying. Really appreciated.
Here is what I found:
<table class="ed-err-tbl" align="center" style="width:550px;">
 
<tr>
 
<td class="err-img"><img src="/slm/images/icon_alert.gif" width="32" height="32" alt="" border="0" /><br /></td>
 
<td><strong>The Field could not be saved.</strong><br/>Please correct the errors identified below and click one of the "Save" buttons.</td>
 
</tr>
 
</table>
 
<!-- HIDDEN ERRORS: {configuration.defectSeverityRatingScheme.ratings[10]=The allowed values must be unique. RatingScheme{name=&#039;null&#039;, ratings={[Cosmetic - do not use, Major Problem - do not use, Minor Problem - do not use, Minor (C), Critical (A), , A - Showstopper - do not use, Undecided, Crash/Data Loss - do not use, Major (B), None, Safety]}}.configuration.defectSeverityRatingScheme.ratings[10] is already an allowed value., configuration.defectPriorityRatingScheme.ratings[11]=The allowed values must be unique. RatingScheme{name=&#039;null&#039;, ratings={[Normal (do not use), Low (do not use), Critical, Undetermined, Major, None, Blocker, Minor, Trivial, Resolve Immediately (do not use), High Attention (do not use), ]}}.configuration.defectPriorityRatingScheme.ratings[11] is already an allowed value.} -->
 
Best regards
Lukasz

[David LeDeaux]

Hi Lukasz,

I don't think it's giving an error due to the new field; it looks like there's a dropdown field it's complaining about that might have a duplicate entry in it somehow.

[David LeDeaux]

Hi Lukasz,

You might have to go into that field definition on the defects and resolve it there.  It's possible it's doing a check across the entire schema.

[Lukasz Socha]

Hi David, 

I do not understand what exactly I should solve in the definition of Severity and Priority fields. In the error message I see that "defectSeverityRatingScheme.ratings[10] is already an allowed value". What should I correct here? In the Severity field I have 10 values and all are unique. I have the same situation in Priority field but here I have 11 unique values. I do not see what is wrong there. 
Thanks for not giving up and continuing to help me. Appreciated :) 

Best regards
Lukasz