Hi all,
I was wondering for those of you who have reviewed/used the Custom Field Optimizer (https://confluence.atlassian.com/adminjiraserver/optimizing-custom-fields-956713279.html) in Jira Data Center, how reliable and accurate have you found the output and actions you're able to take for un-optimized CF's (removing global contexts)?
We've run it against our environment and there's a decent % of fields it's identified as sub-optimal (we knew this was the case, but, having a single list available in product has been a help). We're testing out possible un-expected impact in our UAT environment, but would appreciate any other users feedback if they're also used it. Anything to keep an eye out for? Anything it did you didn't expect?
One point that we didn't expect (this behavior is documented, but still a bit confusing from a UX perspective until you find the documentation) is that if a field has a global context, but is associated with 10 or more projects, it will not show up as not optimized. While this may make sense if you have 20-30 projects - that's 20-30% of projects, our environment has ~ 12,500 projects and growing. I feel that a calculation should be based on a % of the total projects.
CCM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.