Difference between revisions of "OOo Issues"
(→Issue Life Cycle) |
(OOo Category) |
||
| (7 intermediate revisions by 2 users not shown) | |||
| Line 33: | Line 33: | ||
::: 6/ Crashes'' | ::: 6/ Crashes'' | ||
| − | + | * '''Provide sample documents, if possible''' | |
| − | + | * '''Use Attachments where possible''' | |
| − | + | * '''Put all relevant information into the issue''' | |
== How to File an Issue == | == How to File an Issue == | ||
| Line 41: | Line 41: | ||
::Once you logged in you will be in your '''My Start Page''' | ::Once you logged in you will be in your '''My Start Page''' | ||
::Look at the left panel where it says '''My Tool''' and click on '''File Issue''' | ::Look at the left panel where it says '''My Tool''' and click on '''File Issue''' | ||
| + | |||
| + | == Issue Priorities and Examples== | ||
| + | [http://www.openoffice.org/scdocs/ddIssues_EnterModify.html#priority Source] | ||
| + | |||
| + | '''P1''': Extremely severe problem, which must be fixed immediately. | ||
| + | *Reproducible crashes or freezes | ||
| + | *Security Issues | ||
| + | *Build problems | ||
| + | *Incorrect graphics with legal implications | ||
| + | |||
| + | '''P2''': Severe problems which affect a significant number of customers. | ||
| + | *An essential product feature does not work or exist | ||
| + | *Data is corrupted in an easy way | ||
| + | *Huge memory leaks | ||
| + | |||
| + | '''P3''': Non-trivial problems which probably affect a noticeable number of users. | ||
| + | *Spelling errors in obvious places | ||
| + | *The application crashes in very special circumstance | ||
| + | *The user interface for a common functionality is confusing | ||
| + | |||
| + | '''P4''': Problems which are non-critical or rarely occurring. | ||
| + | *Bugs that are easy to workaround | ||
| + | *Spelling errors in rarely seen places | ||
| + | |||
| + | '''P5''': problems which describe wrong behavior of the application, but rarely affect anybody noticeably. | ||
| + | *in a seldom-used dialog, a control with an offset of a few pixels | ||
== Issue Life Cycle == | == Issue Life Cycle == | ||
| + | [http://qa.openoffice.org/issue_handling/workflowcharts/defect_triaging.pdf Flow Chart] | ||
| + | |||
# Open state issues | # Open state issues | ||
| − | ##UNCONFIRMED : This issue has recently been added. No one has validated that this issue is true. Users who have the "Project Issue Tracking - Change" permission set may confirm this issue, changing its state to | + | ##'''UNCONFIRMED :''' This issue has recently been added. No one has validated that this issue is true. Users who have the "Project Issue Tracking - Change" permission set may confirm this issue, changing its state to ''NEW''. or, it may be directly resolved and marked ''RESOLVED''. |
| − | ##NEW : This issue has recently been added to the assignee's list of issues and must be processed. Issues in this state may be accepted, and become | + | ##'''NEW :''' This issue has recently been added to the assignee's list of issues and must be processed. Issues in this state may be accepted, and become ''STARTED'', passed on to someone else, and remain ''NEW'', or resolved and marked ''RESOLVED''. |
| − | ##STARTED : This issue is not yet resolved, but is assigned to the proper person. From here issues can be given to another person and become ''NEW'', or resolved and become ''RESOLVED''. | + | ##'''STARTED :''' This issue is not yet resolved, but is assigned to the proper person. From here issues can be given to another person and become ''NEW'', or resolved and become ''RESOLVED''. |
| − | ##REOPENED : This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked | + | ##'''REOPENED :''' This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked ''STARTED'' or ''RESOLVED'' |
#Resolved state issues | #Resolved state issues | ||
| − | ##RESOLVED : A resolution has been taken, and it is awaiting verification by QA. From here issues are either re-opened and become | + | ##'''RESOLVED :''' A resolution has been taken, and it is awaiting verification by QA. From here issues are either re-opened and become ''REOPENED'' are marked ''verified'' OR are closed for good and marked ''CLOSED''. |
| − | ##VERIFIED : QA has looked at the issue and the resolution and agrees that the appropriate resolution has been taken. Issues remain in this state until the product they were reported against is actually released. at which point they become | + | ##'''VERIFIED :''' QA has looked at the issue and the resolution and agrees that the appropriate resolution has been taken. Issues remain in this state until the product they were reported against is actually released. at which point they become ''CLOSED''. |
| − | ##CLOSED : The issue is considered dead. the resolution is correct. A closed issue can be reactivated by marking it | + | ##'''CLOSED :''' The issue is considered dead. the resolution is correct. A closed issue can be reactivated by marking it ''REOPENED''. |
| + | |||
| + | [[Category:OpenOffice.org]] | ||
Latest revision as of 15:07, 11 May 2009
Contents
Before Filing an Issue
- Before you begin filing an issue, please do take a moment to check if there are existent issue already been reported.
- You may use the Issue Tracker Query http://www.openoffice.org/issues/query.cgi
- You may use the Advance Search http://www.openoffice.org/servlets/Search
Guideline to Filing an Issue (Important)
- One problem - One issue
- Meaning, you are to ONLY file one problem at a time even if you found several problems in the same area.
- For example: I found several problems with the 'save as' option
- 1/ File name increment option does not increment, but rather decrement.
- 2/ The save button sometimes grayed out for no reason
- 3/ Obscure characters are allow to be enter as a file name
- This considered as 3 issues and should be file separately.
- Provide a meaningful summary
- Be descriptive of your discovery to the problem and avoid using generalize statement(s) that may potentially mean a different thing.
- Generalizing the description will result your issue being ignore and review at later time.
- Remember, open office has a large library of source code to search through, providing a concise description will save the community members time.
- Some ideas what you can put in your description...
- Where did it happen?, What trigger the event?, What is the result?, etc
- Provide step-by-step descriptions
- This reinforces the guideline of providing a meaningful summary, software today are becoming more robust as programmer tries to implement additional features that perform the same job simply for the sake of convince for the end user. If you encountered a problem with font changing, please provide a step by step guide for the community the steps you took to generate that result.
- An example of a non-descriptive instruction: I try to apply bold text
- An example of more descriptive instruction:
- 1/ Highlight the text in which you want to apply changes to.
- 2/ Open the edit menu.
- 3/ Select Font
- 4/ Check off the bold check box
- 5/ Press OK
- 6/ Crashes
- Provide sample documents, if possible
- Use Attachments where possible
- Put all relevant information into the issue
How to File an Issue
- Create an account with OpenOffice.org at http://www.openoffice.org/
- Once you logged in you will be in your My Start Page
- Look at the left panel where it says My Tool and click on File Issue
Issue Priorities and Examples
P1: Extremely severe problem, which must be fixed immediately.
- Reproducible crashes or freezes
- Security Issues
- Build problems
- Incorrect graphics with legal implications
P2: Severe problems which affect a significant number of customers.
- An essential product feature does not work or exist
- Data is corrupted in an easy way
- Huge memory leaks
P3: Non-trivial problems which probably affect a noticeable number of users.
- Spelling errors in obvious places
- The application crashes in very special circumstance
- The user interface for a common functionality is confusing
P4: Problems which are non-critical or rarely occurring.
- Bugs that are easy to workaround
- Spelling errors in rarely seen places
P5: problems which describe wrong behavior of the application, but rarely affect anybody noticeably.
- in a seldom-used dialog, a control with an offset of a few pixels
Issue Life Cycle
- Open state issues
- UNCONFIRMED : This issue has recently been added. No one has validated that this issue is true. Users who have the "Project Issue Tracking - Change" permission set may confirm this issue, changing its state to NEW. or, it may be directly resolved and marked RESOLVED.
- NEW : This issue has recently been added to the assignee's list of issues and must be processed. Issues in this state may be accepted, and become STARTED, passed on to someone else, and remain NEW, or resolved and marked RESOLVED.
- STARTED : This issue is not yet resolved, but is assigned to the proper person. From here issues can be given to another person and become NEW, or resolved and become RESOLVED.
- REOPENED : This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked STARTED or RESOLVED
- Resolved state issues
- RESOLVED : A resolution has been taken, and it is awaiting verification by QA. From here issues are either re-opened and become REOPENED are marked verified OR are closed for good and marked CLOSED.
- VERIFIED : QA has looked at the issue and the resolution and agrees that the appropriate resolution has been taken. Issues remain in this state until the product they were reported against is actually released. at which point they become CLOSED.
- CLOSED : The issue is considered dead. the resolution is correct. A closed issue can be reactivated by marking it REOPENED.
