<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Enhancing identification of existing bugs"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=117144">117144</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Enhancing identification of existing bugs
</td>
</tr>
<tr>
<th>Product</th>
<td>LibreOffice
</td>
</tr>
<tr>
<th>Version</th>
<td>6.0.3.2 release
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>UNCONFIRMED
</td>
</tr>
<tr>
<th>Severity</th>
<td>enhancement
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>LibreOffice
</td>
</tr>
<tr>
<th>Assignee</th>
<td>libreoffice-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>that.man.colin@gmail.com
</td>
</tr></table>
<p>
<div>
<pre>It is often difficult to formulate the correct enquiry to ascertain if a report
or request has already been filed.
In many instances, the user will know what menu choice was taken when the bug
manifested itself and even an experienced user who will use keyboard shortcuts
would be able to search help and quickly find the appropriate menu item.
Would it be conceivable to provide a reference link alongside the menu choice
or even in a non-functioning reference menu system here at bug central, in
order that a user could simply identify the reference link and all reports
associated with that specific link - by your triage team - could then be
presented for consideration.
The user could then more easily eliminate any duplication (s)he is about to
create. The provision of a direct link to the specific function would probably
complement existing version control procedures whereby you will already be
ensuring the appropriate modules are assigned to the relevant coders and
subsequently update the correct release(s).
It might also facilitate a faster solution as newer reports can more easily be
"pushed" to those currently engaged in the existing tasks. Don't misunderstand,
I'm not implying the existing system could be inefficient. Eliminating much of
the effort required to remove dross from the system can only help to streamline
the response.
Obviously, this is a very simplistic summation and all your existing
management, prioritisation and integration of reports would still need to be
fully considered.
My primary intention was to identify that it could be easier to eliminate waste
if the user had a better perception of the existing issues related to what is
about to be reported.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>