Versions Compared

Version Old Version 3 New Version 4
Changes made by

Nora Roggeveen-Sams

Nora Roggeveen-Sams

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

...

Section
Column
width50%
Info

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

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

Column
width50%
Panel
borderColor#A40000
bgColor#F8F8F8
titleBGColor#E8E8E8
titleContents
borderStyledashed
Table of Contents
maxLevel5
outlinefalse

Creating a bug/enhancement Jira

Before you begin: 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 1: To Report an Issue within OLE

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

Image Added

...

Skip to step 3

...

Step 2: Create an Issue

If you are not currently in OLE, you may

  1. Create an issue in our JIRA instance using the "OLE Feedback" project.this Jira instance.
  2. Celect OLE Feedback as the Project
  3. 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.

    Image Modified

Submitting an Incident Report

If you come across the Submit Incident Report when working within OLE please include:

Note

Need to check with developers to find out what already is reported/what users should include

What happens next?

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 parent environment, OLE, you will be included as a watcher.

Incident Reports: