Bug 87078 - Cross-reference dialogue in Sidebar
Summary: Cross-reference dialogue in Sidebar
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
Hardware: Other All
: medium enhancement
Assignee: Not Assigned
Keywords: needsUXEval
Depends on:
Blocks: Sidebar-New-Decks Cross-reference-dialog
  Show dependency treegraph
Reported: 2014-12-07 18:35 UTC by andis.lazdins
Modified: 2021-10-06 17:27 UTC (History)
4 users (show)

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


Note You need to log in before you can comment on or make changes to this bug.
Description andis.lazdins 2014-12-07 18:35:03 UTC
Cross-reference dialogue can be now called from the main menu or Insert tool-bar. It would be great to adopt the Insert Cross-reference dialogue to the Sidebar, as it is one of the most commonly used feature in Writer application.

Another excellent improvement to save a lot of time in making Cross-references would be, if the program would remember the last choice for selection in the "Insert reference to" window for specific type of references, like tabs, figures etc. Currently the "Insert reference to" returns to the first position after every start of the dialogue.
Comment 1 Robinson Tryon (qubit) 2014-12-21 17:49:02 UTC
One for the UX Team!
Comment 2 Heiko Tietze 2016-05-24 11:08:48 UTC
Cross-references are definitely frequently used and worth to get integrated into the sidebar. But before we start with a new UI wouldn't it make sense to integrate the function into the navigator? For instance you right click the headings entry that should be inserted and below the current options (which should be removed by the way since none of them is not context sensitive) would offer 'Insert cross-reference >' with 'Page', 'Chapter', 'Reference' etc. below.

Would that work?

Setting component to Writer and keyword needsUXEval
Comment 3 Cor Nouws 2019-02-05 18:35:52 UTC Comment hidden (off-topic)
Comment 4 Timur 2021-10-06 17:27:14 UTC
*** Bug 144733 has been marked as a duplicate of this bug. ***