Child pages
  • JIRA Authoring 101

Versions Compared

Key

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

...

  1. Issue type: Bug if it is not behaving correctly, Feature Request if it is behaving as expected, but needs improvement.

  2. Summary: The title (brief description of issue)

  3. Priority: Defaults to Major; if not sure, leave it.  Blocker is for something that totally destroys functionality and will prevent release of the affected Sakai version.

  4. Components: Affected tools or features (e.g. Accessibility, Internationalization)

  5. Affects versions: Include ALL the most recent Sakai versions it affects.

  6. Assignee: Leave default (Automatic)

  7. Environment includes:

    1. URLs of server(s) where you tested it,

    2. Computer operating system,

    3. Internet browser and version,

    4. If you are using additional technology (such as a screen reader), the software and version.

  8. Description: Try to explain it as clearly as possible.  If you have screen shots, you can attach these and embed them in the description (see below, the Tips under the description of the Testing Tab, for steps to embed).

  9. Attachment: Screen shots, a text file with a copy of a bug report (if one appears while reproducing the issue) or other files (e.g., an exported quiz for someone to reproduce the issue) - you can embed or link these attachments right in the jira text too!

  10. Security Level: Usually leave default (None) - security jiras are sensitive issues like holes for hackers to exploit.

  11. Labels: Optional - these can help you search for the issue, some examples: TL if you want Teaching & Learning call to look at it, Accessibility or a11y, Internationalization or i18n.

  12. Fix Version/s: Leave default (empty) - these get added after the issue is fixed.

...