Earn badges and make progress
You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Participate in fun challenges
Challenges come and go, but your rewards stay with you. Do more to earn more!
Gift kudos to your peers
What goes around comes around! Share the love by gifting kudos to your peers.
Rise up in the ranks
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Is there a way to keep the stock formatting on a version field that'ss been custom sorted/filtered
Edited
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.)?
1 answer
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.