Bug 157955 - Outline numbering for Write heading styles not working
Summary: Outline numbering for Write heading styles not working
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.5.7.1 release
Hardware: All Windows (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-10-27 20:49 UTC by Steve
Modified: 2023-10-29 20:03 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Steve 2023-10-27 20:49:30 UTC
Description:
Libreoffice 7.5.7.1

Outline numbering for Write Heading styles 1 -10 does not work correctly

Outline numbering 1, 1.1 etc has been set for heading styles 1-10 in the option to do this

However when populating a documnet subheadings are numbered from the the first heading 1.

EG. 

   1. A heading 1
   2. Another heading 1
   3. yet another heading 1
     1.1. a subheading 2

The workaround is to select the subheading 2, go to Styles\ numbering 123 list select this and sub-heading 2 will be numbered correctly i2 3.1. a subheading 2.

The workaround is fiddly.
  

Actual Results:
Open a document in writer
Change heading numbering to outline numbering for all headings 1-10
In the document create a few lines of data
change them all to heading 1
insert another line of data after the last heading
change this to heading 2 

Expected Results:
The heading 2 will be numbered from the first heading. 


Reproducible: Always


User Profile Reset: No

Additional Info:
It should have numbered sub heading 2 from the number of the last heading 1. This is the way it has always operated.
Comment 1 Dieter 2023-10-27 21:00:27 UTC
Steve, thank you for the bug report. Please add a sample document, as that makes it easier to reproduce the bug. Thank you.
=> NEEDINFO
Comment 2 Steve 2023-10-29 17:33:12 UTC
The problem has now gone away so this problem can be closed. I have no idea why the problem went away, it just did. Perhaps a reboot was responsible.
Comment 3 Steve 2023-10-29 17:34:33 UTC
(In reply to Steve from comment #2)
> The problem has now gone away so this problem can be closed. I have no idea
> why the problem went away, it just did. Perhaps a reboot was responsible.
Comment 4 Dieter 2023-10-29 20:03:14 UTC
(In reply to Steve from comment #2)
> The problem has now gone away so this problem can be closed. I have no idea
> why the problem went away, it just did. Perhaps a reboot was responsible.

Thank you for restesting.
=> RESOLVED WORKSFORME