...
- Fill in the "Summary" field. Title the issue.
- Choose which component(s) this issue is related to.
- Choose a "Priority".
- Blocker - A module or significant functionality is impaired to the point of preventing users from carrying out core business processes.
- Critical - Key functionality is unusable or severely crippled. Typically (a) there is no acceptable workaround; (b) it prevents access to functionality deeper in the software; and (c) overall it has as significant impact.
- Major - Functionality is hindered or obstructed. Typically (a) the workaround, if it exists, is time consuming or complicated or results in having to re-enter data; (b) most often occurs fairly deeply in the software and does not obstruct large pieces of functionality; and (c) overall has lower impact than a critical.
- Minor - It is a minor loss of functionality or other problem where easy workaround is present.
- Trivial - It is a cosmetic problem like misspelled words or misaligned text.
- Assignee may be left as "- Automatic -". This will notify the QA manager.
- Add notes. Describe the issue. Copy and paste in relevant error codes, list the steps you took to recreate this issue, describe the expected result and then what actually happened, copy and paste the entire stack trace error if applicable.
Additional helpful items include:- Document ID
- Logged in Kuali User
- Browser
- Click the "Create" button.
What happens next?
Incident Reports
What happens next?(feature in progress see OLE-3689)
...
Jiras
Once your Jira ticket has been submitted, it will be reviewed by the QA Manager. He will determine course of action. If a Jira is created in the OLE development queue, OLE, you will be included as a watcher.
...