Bug 88336 - Navigate by date and headings navigation bug.
Summary: Navigate by date and headings navigation bug.
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-12 19:33 UTC by rizquierdoma
Modified: 2015-09-04 03:00 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description rizquierdoma 2015-01-12 19:33:28 UTC
Greetings to the entire team of LibreOffice.

I am a student and I use LibreOffice Writer to take notes for several years.

In each lesson, I add a date field to identify the day of the lesson.

I wish I could browse by date. With LibreOffice Writer you can navigate by tables, images, comments, etc. but not by date. It would be a major improvement for me.

Moreover, I use headings to generate automatic index and navigate using the browser (F5). However, there is a major bug in the navigator headings: every time I add a heading, rather than select automatically the current heading, it is placed in another with the same name. In each lesson, headings are repeated (eg, "treatment") and instead identify the current heading by index, it identifies it by text property (I guess, because I am a programmer too) and it is a bug that bothers me a lot to take notes.

I appreciate your improvements.

Thank you.
Comment 1 Robinson Tryon (qubit) 2015-01-15 08:15:39 UTC
(In reply to rizquierdoma from comment #0)
> Greetings to the entire team of LibreOffice.
> 

Hiya.

> I wish I could browse by date....It would be a major
> improvement for me.

So that's an enhancement request, and should be 1 bug report.

> Moreover, I use headings to generate automatic index and navigate using the
> browser (F5). However, there is a major bug in the navigator headings: 

That topic is a bug/defect, and should be a 2nd bug report.

Status -> NEEDINFO


Decide which topic this particular bug report should focus on, and open a new bug report for the other issue. Then update this bug's Summary and leave a new comment to make it as clear as possible. Finally, change the status of this report back to 'UNCONFIRMED' so we can triage it.
Comment 2 QA Administrators 2015-07-18 17:35:28 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team

This NEEDINFO message was generated on: 2015-07-18
Comment 3 QA Administrators 2015-09-04 03:00:47 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID 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 FDO
Message generated on: 2015-09-03