Reporting an Issue in OLE

https://jira.kuali.org/browse/OLEFDBK

Step 0: Search For A Similar Issue

1. Before you enter an issue, please perform a search to see if anything may already exist in the OLE queue
2. Enter your search criteria in the Text Search section's Query field.
3. If you find an issue that is similar to the one you want to report, please add a comment to the issue to clarify any differences and talk with the SME team lead if you need clarification.
4. If you don't find an issue that is similar to the one you want to report, proceed with the instructions below.

Step 2: Create an Issue

1. Create an issue in our JIRA instance using the "OLE Feedback" project.
2. Select the appropriate type:
   • For bugs, select Bug
   • For enhancements, select either Improvement or New Feature (which ever makes the most sense)
   • DO NOT select Task

Step 3: Fill Out Required Fields

Only deal with the following fields:

1. Fill in "Summary" field. Briefly describe the issue. (Please list which module/tab/panel the issue pertains to at the beginning of the summary line, for example, "Budget - Organization - Location Panel:"). A good summary concisely describes the issue.
2. Choose which component(s) this issue is related to.
3. 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.
4. Add notes. 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.
   • Helpful items include:
     Document ID
     Logged in Kuali User
     Browser
5. Click the "Create" button.