https://bugs.documentfoundation.org/show_bug.cgi?id=163127
--- Comment #4 from ady <[email protected]> --- As for this report being an enhancement request, the main goal seems clear, but I'm not sure about the exact steps to reproduce the original behavior that generates such split of CF, (and therefore, which exact procedure would be considered for/as an enhancement). As it is now, it sounds not precise enough. Although in the past there have been some attempts to force the unification of CF rules and ranges, the results are mixed between positive and negative. It is not always a welcome result, and in fact some use-cases request the opposite (the "unification" was not what was desired, and the user has to re-create the CF rules by hand, replacing the forced result). In order to reflect different use-cases and needs, the unification (either regarding ranges, or regarding rules) should rather be activated manually (not forced), for example by selecting some of the rows in the CF manager (and/or in the CF dialog for each range + set of rules) and pressing some button in the UI. In addition, the current 25.2 alpha branch has also some WIP modifications. Incidentally, I have my own doubts about them too. Can you please create a minimal sample ods file in a similar way as your original ods file? It should not contain private/sensitive information, and it should show the problematic behavior. Then attach the sample ods file to the report, and, if possible, add a step-by-step procedure about how to create such sample file. -- You are receiving this mail because: You are the assignee for the bug.
