Apache OpenOffice (AOO) Bugzilla – Issue 36135
no descriptions for subcomponents available.
Last modified: 2007-06-28 07:07:57 UTC
On example URL and others there is nearby no help available for selection of an useful subcomponent. Of course, some are self-explication (more or less), but some more explication would be helpful. For example: "open-import" for all problems with "open document" or only for problems with import of not-OOo-formats? Rainer
moving to qa
I can take care of the RFE process related subcomponents if someone tells me what I have to do exactly. Thanks, Erwin
Have a look at the URL mentioned above and you'll find subcomponents like configuration, editing, ... Please provide a 1-2 sentence description for those subcomponents. Thanks, Stefan
Martin, Erwin, would you take care of the descriptions.
I don't know where exactly the descriptions are stored and what needs to be changed. Thus, I provide the descriptions as a comment. code ==== Subcomponent used to classify bugs: Use this component if you are able to reference a piece of source code, in which the issue occurs. Patches are highly appreciated. This component is mainly meant for issue reporters with developer skills. configuration ============= Subcomponent used to classify feature/enhancement requests: Use this component if the feature/enhancement is mainly related to configuration tasks. editing ======= Subcomponent used to classify feature/enhancement requests: Use this component if the feature/enhancement is mainly related to editing tasks (i.e. adding, removing and changing content). formatting ========== Subcomponent used to classify feature/enhancement requests: Use this component if the feature/enhancement is mainly related to formatting tasks (e.g. applying styles, changing colors). open-import =========== Subcomponent used to classify feature/enhancement requests: Use this component if the feature/enhancement is mainly related to file open/import tasks. printing ======== Subcomponent used to classify feature/enhancement requests: Use this component if the feature/enhancement is mainly related to printing tasks. programming =========== Subcomponent used to classify feature/enhancement requests: Use this component if the feature/enhancement is mainly related to programming tasks. save-export =========== Subcomponent used to classify feature/enhancement requests: Use this component if the feature/enhancement is mainly related to file save/export tasks. ui == Subcomponent used to classify bugs: Use this component if you are not able to reference a piece of source code, in which the issue occurs. viewing ======= Subcomponent used to classify feature/enhancement requests: Use this component if the feature/enhancement is mainly related to viewing tasks (e.g. zooming, print previews).
These descriptions should be stored in the IssueZilla database. Try to fill new issue, select Word processor as a component and you'll see the Issue form. Subcomponent word is a link to this page: http://www.openoffice.org/issues/describecomponents.cgi?component=Word%20processor All subcomponents are listed here with descriptions if available. So, this should be changed directly in the IssueZilla database (for each component if the descriptions are not shared).
Hi mru, do you agree with de descriptions for subcomponents owned by you in comments from dancer Wed Nov 3 03:20:38 -0800 2004 ? Rainer
For the "save" and "open" parts should be mentioned that it is also related to Alien formats like MS Word or RTF or .txt. For "programming" we should perhaps add the word "macro". For "ui" there should be mentioned that this is related e.g. to dialog or toolbar issues. For "configuration" we should mention, that this relates to things in the options or customize dialogs. I think, with these addings we can make issuezille-life a little bit easier especially newbies.
I hope I got now all subcompents and added the proposed subscription. In some case I found subcomponent installation I have no description for.
close issue.