I have encountered the strange case in which for some documents the list numbering restart is not preserved upon reopening the document after saving and closing it. Please refer to the attached document.
Steps to Reproduce:
1. Set restart numbering for the first list item
2. Save and close the document
3. Reopen the document
List numbering restart is not active anymore
List numbering restart should be active upon reopening the document
User Profile Reset: No
Created attachment 146170 [details]
List numbering restart issue demo document
I confirm the desribed behaviour. But I think, if it is the first numbering in a document there is no need, that "restart numbering" is active. If you choose "restart numbering" for the second list entry, restart numbering remains active after save and reopen.
So for me NOTABUG
(In reply to Dieter Praas from comment #2)
> I confirm the desribed behaviour. But I think, if it is the first numbering
> in a document there is no need, that "restart numbering" is active. If you
> choose "restart numbering" for the second list entry, restart numbering
> remains active after save and reopen.
> So for me NOTABUG
This is a very big issue because I have many such subdocuments that I import in a master document and their list numbering starts from the end of any previous list instead of from 1. I have to set the list restart numbering at the master document level because this setting is not saved at subdocument level for some of my documents.
This issue only occurs in the case of just some documents, not all, so it's really strange.
(In reply to Daniel Grigoras from comment #3)
> This is a very big issue because I have many such subdocuments that I import
> in a master document and their list numbering starts from the end of any
> previous list instead of from 1.
I understand and agree => Set to NEW
I don't reproduce this with LO 6.0 not 6.4+.
If I set "restart numbering" I can see it set on reopen.
Anyway, this seems like a duplicate of bug 40929.
If not, please explain and set again to New.
*** This bug has been marked as a duplicate of bug 40929 ***