Hi,
- Server: 7.7
- Custom Field Name: Signal
- Custom Field Type: Single Choice Select List
- 3 field configurations: N, G, and Default
- Hundreds of values per configuration created initially using ScriptRunner, but amended manually and re-indexed
- Many projects. Project N uses field context N, G uses G, all others (e.g., R) use Default.
- Project R was created as a copy of Project N (using ScriptRunner) and then the field configuration was changed to Default, but only AFTER many hundreds of issues were imported
Problem: When searching Project R using Basic search, the desired search term, call it "ABC" is omitted from the Signal drop down list. However, when using Advanced search, the term is available in autocomplete list
"ABC" is in field context N, but not Default. This explains its omission from Basic Search dropdown. Is Advanced Search combining all contexts for autocomplete, or is it using values all values associated to issues in the current project?
Obviously we will update our field contexts to conform the value lists to our requirements, but this is a confounding discrepancy.
Any insight you can provide will be most helpful.
Thanks,
Dave
