Bug 31592 - [TASK]: Improve FreeDesktop Bugzilla for the needs of LibreOffice.
Summary: [TASK]: Improve FreeDesktop Bugzilla for the needs of LibreOffice.
Status: CLOSED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Libreoffice (show other bugs)
Version: unspecified
Hardware: Other All
: high enhancement
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 31457 31593 31701
Blocks:
  Show dependency tree / graph
 
Reported: 2010-11-13 01:53 UTC by Rainer Bielefeld Retired
Modified: 2011-01-12 08:00 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Rainer Bielefeld Retired 2010-11-13 01:53:27 UTC 
Soon awaiting the first stable LibreOffice version, we have to improve FreeDesktop Bugzilla for the needs of LibreOffice.
Currently database use is rather coarse, what will case several problems selecting, searching and assigning bug reports.
For this improvement process, I created this TASK Issue as a collection with references to other Reports concerning details of these improvements.
An indispensable precondition for quick results here is that someone with the required permissions to add keywords, subcomponents and similar to the database system. Can someone find such a person and add it to the CC list?

Further "Depends On" references will follow soon.
Comment 1 Rainer Bielefeld Retired 2010-11-13 02:14:22 UTC 
Added some CC
Comment 2 Rainer Bielefeld Retired 2010-11-18 00:29:44 UTC 
Added: Bug 31701 - Version picker required for LibreOffice

Unfortunately there isn't any progress for this issue, can anyone with "connections" please try to accelerate?
Comment 3 Alex Thurgood 2011-01-06 06:37:08 UTC 
The settings for better triaging of bugs in libreoffice now appear to be available in the freedesktop bug reporter, so setting to resolved fixed.

Alex
Comment 4 sophie 2011-01-12 08:00:43 UTC 
Closing - Sophie

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.