1. We are going to release a new interface for managing fields, which is going to include a multiselect for schemes. API is also available if you prefer to write a script.
2. The manual optimization includes a preview, a confirmation step; the administrator chooses which projects will be optimized and when. Because of this, the manual optimization can be more aggressive in removing fields.
You are correct about required fields being important. There is however also other configuration (work type screen scheme, custom field context) which can exclude this field from certain projects and make it optional anyway.
We have identified several projects that use a trick where a Read-only message field is put on a workflow transition screen (I imagine it's some sort of notice, or description). Such field is not going to have any field values (because it's read-only) and it's not present on any screens in the work type screen scheme so we added a new workflow rule to prevent disrupting that scenario.
I just got the message that "Add and remove fields from field configurations; new tools to optimize fields in your projects" is now generally available but for life of me I can't find this optimization tool.
We are rolling this out progressively so it may take a few days or weeks before it's available on your Jira. The experience may arrive in parts - for example the new field configuration page should be already available everywhere.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
This sounds mostly good. I'm not a fan of the automatic involuntary optimization. I'm very much a fan of the manually triggered optimization with approval steps.
I just saw this post today. As others have said, this absolutely needs to be communicated much better. Banners, emails to Product admins, and for f... sake give is a date of when it'll happen. This "Oh, it'll happen, eventually, probably" nonsense is getting really old. Does Atlassian now care enough to let their customers know about changes to their site, or are you incapable?
Questions:
For the automatic optimization, how can I turn it off for our site?
For the manual optimization, will there be a page where I can select/deselect which things to optimize, in case a bit too wide of a net has been cast? Or is it a "take it or leave it" kind of situation?
For the automatic optimization, how can I turn it off for our site?
Opt-out is not integrated in the UI. Please either create a support ticket (and include a link to this post so that it reaches the correct team quickly) or email me at pvanecek@atlassian.com and I can turn this off for your instance.
a page where I can select/deselect which things to optimize
There are several options for optimizing:
- Either use the Scheme optimizer tools which indeed are "all or nothing" kind of optimization
- Or use the Field configuration page and remove fields one by one
- Or use REST APIs which will allow you to fine-tune the removal
May I ask what rules would you follow when choosing which fields to select or deselect?
30 comments