Pavel V Atlassian Team

Hi @Chris Rogers the optimizer is looking at both: - fields that are referenced via transition screen in a workflow - fields referenced via forms If either of those is detected then the field is considered used. As of today Jun 4th 2026 the optimizer does not check for "field referenced in automations" explicitly. What…

Hello @Goran Dermeta, thanks for your comment. The message "Scheme Name,Entities removed" you are seeing are CSV headers. There's supposed to be a list right under it. We're looking into why did your report not generate. Sorry for the inconvenience Pavel

@Josh Imposing the limit without addressing the SLA situation will pose a hardship for us If you went through the scheme optimizer (https://support.atlassian.com/jira-cloud-administration/docs/optimize-fields-in-your-project/) and your schemes are still over the limit, please raise a support ticket and we will find a…

@__ Jimi Wikman you should already see the UI changes on your instance (if it has more than 700 fields it will warn you). I hope that helps to understand what is going to happen in February. For your questions this is all fields, or just custom fields? All fields what happens when you add a custom field with a global scope…

@__ Jimi Wikman, in case of hitting a limit, Jira admin will prevent adding more fields to the field configuration scheme. All work items, and all projects, will continue working same as before. Filters are unaffected. All projects remain operable. One can add new SLAs even after reaching the limit. Pavel

Hi @Joël Kemnitzer, fields created in team-managed projects cannot be associated with field configuration schemes and so do not contribute towards their limit. The limit is applied for each scheme. The overall amount of custom fields on your site remains unlimited. @Josh thanks for your comment, we're working on the SLA…

Thanks for the feedback @Joerg, I will see if we can surface this information. P

Hi @Fernando Eugênio da Silva, the limit is applied on a field configuration scheme level, meaning you won't be able to add more than 700 to a single field configuration, or a single field configuration scheme. We are now rolling out UI changes where you will see a preview of what exactly is going to happen in February and…

Hi @Jared Schmitt, thanks for your comment. You will find that the automatic optimizer is one-time activity and is already completed. I checked my testing instance and I can see the list of fields being removed, and the field configuration affected, in my audit log. Is this the information you were looking for? Which other…

Hi @Risto Majamaa, this looks like a bug on our side, I will look into it. If you have the option to create a support ticket and provide more information, that will speed things up. @George Shaw yep I'm with you on this one. We are working on displaying a list of fields. Until that's ready, as a workaround, you can see the…

Hi @Rune Rasmussen 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…

Hi @Joerg, we have added a new article on how to use the scheme optimizer: Optimize fields in your project. 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…

Hello @P_D_ Foerster, thanks for your comment. 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…

Thanks Sascha, I now understand what you mean. Some of those changes will be easier than others. I'll see what I can do. Pavel

Hello everyone! Thanks for your comments. @Sascha Weber I am not sure if I fully understand your suggestion. What would ID leading and name leading look like? Can you please elaborate? What comes to my mind, as maybe related, are two things: Have you yet had a chance to read the announcement by Carol? We’re improving…

@Samuel Segaud we're in the process of rolling it out, you may notice some of the smaller changes available on your instance today. It's going to take a couple of weeks to reach everyone.

Hello @Samuel Segaud , the tools showed in this article are going to be available in all editions. Pavel

Hello @Yatish Madhav , yes you are correct, the "Isolate scheme" action is doing exactly that for a single project. "Divide all projects" will isolate all projects in the scheme in one go if you would like to do that. It may decide to group projects together and create fewer schemes than the one-by-one option. Thanks for…

Hello @Susan Waldrip! Removing the field association does not modify the data on work items. So if you (or Jira) remove a field, then add it back - data on work items will appear again. Pavel

Thank you for the feedback @James Rickards _SN_ 

Hi @James Rickards _SN_, this post is the only warning that is coming. Do you have some concerns about the removal? What actions were you hoping to do after receiving the warning? Pavel

Hello @Izabela França, yes that is correct! You will need to add a new field to both screen, and a field configuration scheme, to make it visible on a work item. We are preparing some changes to the field create experience to make this new step more apparent. Stay tuned for future announcements :) Pavel

That's right! Let me just add that this functionality is available for Classic projects only. Next Gen projects are independent and do not allow sharing custom fields.

This may or may not be related to a bug where reserved field names show the same error: https://jira.atlassian.com/browse/JSWCLOUD-18497 We are working on a fix. In the meantime, can you please take a look at your fields and see if any custom field has name that is used by Jira internally? Renaming should do the trick and…

Hello Jeremy! Does the error appear on all issue types, or only Story? If you click "Create issue type" does that work? Pavel

Hi Mirek and Ravi, please follow the roadmap page for updates: https://www.atlassian.com/roadmap/jira-software

Hi Tony, as far as I know this is not possible. The story point is considered complete only when the issue is Done. I would suggest breaking stories into smaller ones.

Hi Claus, have you tried adding a custom field? It might help you do what you need. Here is an article I found: https://confluence.atlassian.com/adminjiraserver071/adding-a-custom-field-802592519.html

Hi! Bitbucket uses git under the hood and git is an excellent place to store text files, such as Dockerfile. It does support storing binary files but it is not a good match for Docker images. You can probably save the Docker image using docker save and commit that - but instead I suggest you take a look for a real…

Hi Uday, guessing: are those 'XXXX' parts exactly the same, including Letter Size? It may be that windows are case-insensitive and think of that as a single folder, but Bitbucket uses case-sensitive filesystem.