You may go directly to the OLE FeedBack Project to review/create/modify Feedback Jiras

Remember to Login to Jira, otherwise you will miss pieces of the interface.

Development Process with Jira

Below is the OLE Development Process as it exists within the Jira ticketing system.

Click here for the Development Process in pdf.

Intro to Jira contains basic information about the software and the ticket types OLE uses.

Creating a Bug JIRA ticket

Before you begin: Search For A Similar Issue

Before you enter an issue, please perform a search to see if anything may already exist in the OLE queue
Enter your search criteria. For an introduction to searching Jira, see the Basic Searching page in the official JIRA User's Guide
If you find an issue that is similar to the one you want to report, please add a comment to the issue.
If you don't find an issue that is similar to the one you want to report, proceed with the instructions below.

Step 1: Report an Issue from within OLE

Select the Provide Feedback link on the top right side of the OLE Interface:

Skip to step 3

Step 2: Create an Issue from outside OLE

If you are not currently in OLE, or are having difficulties with access:

Create an issue in this Jira Instance.
Select OLE Feedback as the Project
Select the appropriate type: bug/defect

Step 3: Fill Out Required Jira Fields

Fill in the "Summary" field. Title the issue.
Choose which component(s) this issue is related to.
Change the Fix Version/s to "OLE ?" or leave it blank.
Choose a "Priority".
- Blocker - Key functionality is broken. Without the functionality, all business processes for a module are at a standstill and there is no workaround.
- Critical - Key functionality is unusable or severely crippled. Some significant business processes for a module are at a standstill; there is no acceptable workaround.
- Major - Key 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 - Tthere is a minor loss of functionality or other problem where an easy workaround is present.
  Trivial - There 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. Include a justification of the priority chosen.
Additional helpful items include:
- Document ID
- Logged in Kuali User
- Browser
Add screenshots as Attachments. Screenshots really help to clarify issues and show what is happening.
1. With Windows: Press the Windows logo key + PrtScn. (On a tablet, press the Windows logo key + the volume down button). This will take an image and save it as a file under Pictures > Screenshot.
2. With a Mac: Press Command (⌘) + Shift + 3. The screenshot is added to your desktop.
Click the "Create" button.

What happens next?

Incident Reports

(feature in progress see OLE-3689)

Jiras

Once your Jira ticket has been submitted, it will be reviewed by the QA Manager. If a Jira is created in the OLE development queue, OLE, you will be included as a watcher.

Issues will be set to a Fix Version and reviewed by the Implementation Team.

The Implementation Team assigns a release, revise the priority if needed, advance the ticket status to "Awaiting Technical Input", and assign the ticket to the development manager if no additional functional instructions are required.

JIRAs Currently in OLE Feedback

key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution

Loading...

Refresh

Browser not supported