Work in Progress
Please know we are still working out the process and details of reporting issues
You may go directly to the 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/Enhancement Jira
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.
- 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.
- 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
.
- Select OLE Feedback as the Project
- Select the appropriate type: bug or enhancement
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 - 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. Include a justification of the priority chosen.
Additional helpful items include:- Document ID
- Logged in Kuali User
- Browser
- 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 Fix Version "OLE ?" if not already done by the reporter.
Issues the QA Manager (or the reporter) prioritized as minor or trivial are assign to the Lead SME and ask that person to review priority AND fix version.
Issues the QA Manager (or the reporter) prioritized as major, critical, or blocker are assigning to Stuart and asked for his review of priority and fix version based on the needs of Chicago and Lehigh. (For 1.5)
Stuart or Lead SME assigns a release, revise the priority if needed, advance the ticket status to "Awaiting Technical Input", and assign the ticket to Vijay if no additional functional instructions are required.
OLE RICE Jiras
If an OLE Jira is dependent on a RICE issue, OLE SMEs and Project Team will follow this course of action:
Click here for the Process in pdf.
JIRAs Currently in OLE Feedback