In one of our projects, we do a lot of custom sorting and filtering on some of the version fields... an example is that we have a '.X' version that is used early in a workflow as a placeholder... i.e 7.X. Later in the workflow we force the defect to commit to a 'real' version and we also filter out the fake version options.
This works as intended, but an unfortunate side-effect iof using setFieldOptions() appears to strip all formatting away. including the nicely-fomatted 'Released' and 'Unreleased' headers in the version field's drop down screen.
Its simple enough to replicate how it sorts the versions by release status, but what I DO lose is the Released/Unreleased headings and formatting. Is there a way to retain this formatting (like how we can use convertToSingleSelect() to manipulate a text field.)?
(Sorry, just saw the notifiaction) No, not yet. I would still love to be able to maintain the 'Released' vs 'Unreleased' grouping.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.