I think I've determined that all important filters use "Rank" so I want to delete the other two. Would re-inserting the row in the customfield, fieldconfiguration, and configurationcontext tables be sufficient to rollback if needed?
In query form, these rows:
select * from configurationcontext cc, fieldconfiguration fc, customfield cf where cc.customfield = fc.fieldid and fc.fieldid = concat('customfield_', cf.ID) and cf.ID = <id to be deleted>
Do you mean as stored in customfieldvalue or is there another table? It turns out lexoranks have their own table AO_60DB71_LEXORANK and the ranking data itself is not deleted https://jira.atlassian.com/browse/JSW-13098?src=confmacro&_ga=1.80024983.1470128015.1477686267
Ah, sorry, I misread it and got the context wrong. Didn't realise it was the Software ranking field.
No, that does not get cleared, so, in theory, yes, you could replace the custom field entry. But you'll need to check the field configurations and contexts are added back correctly as well, and, as usual, reindex the whole system.
I would treat the deletion of the custom fields as a one-way action. You can recreate them as new custom fields of that type if needed. I don't recommend having more than one Rank field of type Global Rank since it takes more time to build the Lexorank values. I don't recommend keeping any of the older kind of Rank fields either.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
A picture tells a thousand words. And agility boards have just released their latest feature: cover images on issues – so now your board can tell a story at first glance. Upload attachmen...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs