Versions Compared

Version Old Version 34 New Version 35
Changes made by

Patty Mescher (Unlicensed)

Nora Roggeveen-Sams

Saved on

Key

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

 

 

Section
Column
width50%
Info

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.

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

...

  1. Fill in the "Summary" field. Title the issue.
  2. Choose which component(s) this issue is related to.
  3. Change the Fix Version/s to "OLE ?" or leave it blank.
  4. Choose a "Priority".
    • Blocker - A module or significant functionality is impaired to the point of preventing users from carrying out core business processesKey Functionality is broken down completely.  Business processes for a module are at a stand still and there is no workaround.
    • 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.
  5. Assignee may be left as "- Automatic -". This will notify the QA manager.
  6. 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
  7. Add images as Attachments.  Screenshots really help to clarify issues and show what is happening.
    1. With Windows: Press the Windows logo key Windows logo keyImage Added + PrtScn. (On a tablet, press the Windows logo key Windows logo keyImage Added + 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.
  8. Click the "Create" button.

...

Issues the QA Manager (or the reporter) prioritized as major, minor, or trivial are assign assigned 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 assigned to Stuart Patty and asked Vijay 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.

...