Bug 121973

Summary: Alphabetical Index
Product: LibreOffice Reporter: Jack Ray <jackray2>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INSUFFICIENTDATA    
Severity: normal CC: dgp-mail
Priority: medium    
Version: 6.0.7.3 release   
Hardware: All   
OS: Windows (All)   
Whiteboard:
Crash report or crash signature: Regression By:
Bug Depends on:    
Bug Blocks: 89606    

Description Jack Ray 2018-12-08 01:19:55 UTC
I have a book from about 4 updates ago.  Starting to work on the file which contains many Bible verses.  These verse references are in the format of
 BOOK CHAPTER : VERSE.  After updating to the current version, all the index entries have been changed so that everything to the right of the colon is Index Level 1.  The colon has been deleted.  Everything to the left of the colon is now Index Level 2.  
Any idea of why?
Comment 1 Dieter 2018-12-08 08:31:48 UTC
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. 
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
(Please note that the attachment will be public, remove any sensitive information before attaching it)
Comment 2 QA Administrators 2019-07-30 03:19:06 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2019-09-02 09:36:59 UTC
Dear Jack Ray,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp