Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

How to add a bug in JIRA

Before adding a bug, please review the Bug List below to make sure that your bug has not already been reported.

General Guidelines
  1. Go to Sakaibrary's JIRA homepage (you may want to open this link in a new tab or window to be able to refer back to this guide).
    • You will need to have a JIRA login id to be able to access this website. If you do not already have one (try your Confluence username/password), please sign up for JIRA.
  2. Click on the link to "Create New Issue" (if you're having trouble finding this: refer to the sample Sakaibrary JIRA home page screenshot - the links to create a new issue are highlighted in orange.)
  3. The selected Project should already be set to "Contrib: Sakaibrary". If not, please set it.
  4. The selected Issue Type should already be set to "Bug". If not, please set it and hit the 'Next>>' button.
  5. Provide a very brief title in the Summary field that describes the problem and distinguishes it from other problems.
  6. Setting the Component:
    • If you know that the problem primarily relates to the user interface or the behavior of the Citations tool/helper, select "Citation tool".
    • If it relates to the way searches occur at Michigan, select "Xserver OSID".
    • If it's primarily an issue with searches at Indiana, select "Web2bridge OSID".
    • You can select more than one Component.
  7. For now, the Affects Version/s should be "Phase 1 - 001"
  8. Assign To: For now, you can leave this field as is. You can assign bugs to yourself after they have already been created. For now, do not assign bugs to others.
  9. If it is possible that the issue is related to a particular browser or OS, please include that information in the Environment field. Also include info about what server you connected to when you noticed the problem.
  10. Provide a detailed description of the bug in the Description field including information about how to reproduce the problem and what the desired behavior is.
  11. Attachments are optional and screenshots are preferred. Screenshots are better than providing a URL to a particular sakai site that may be unavailable when the bug report is viewed. Images of type png, jpg or gif are better than bmp's, tiff's, and other bit-mapped formats because there is better support across OS's and they load faster.
  12. Once the bug is created, you'll be taken to your bug's summary page. The bug should be Unassigned.
  13. In the left hand sidebar, under the "Operations" section, you can choose to 'Assign this issue (to me)'. Click on the 'to me' to assign the issue to yourself.

Open Bugs

The issue is open and ready for the assignee to start work on it.

type key summary assignee reporter priority status resolution created updated due

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Reopened Bugs

This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.

None to display.

Resolved Bugs

A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.

type key summary assignee reporter priority status resolution created updated due

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Closed Bugs

The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

None to display.

All Bugs

type key summary assignee reporter priority status resolution created updated due

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  • No labels