Before reporting a Support ticket in Jira
- Confirm that the Bug can be recreated in the current release FOLIO current environment found on https://wiki.folio.org/
- Verify that the Bug has not already been submitted to the Support SIG
Creating a Jira ticket:
There are two paths to reporting a production bug
- Log into Jira https://issues.folio.org
- Click Create in the top navigation
- A pop-up window will appear
- Project = Support (SUP)
- Issue Type = Bug
- Template = Standard Bug Write-Up Format
- Summary = Treat as a Subject line for an email, Sample: "Check out the receipt emails are not sendt to library users"
- Pro tip: Indicate your level of priority in the summary - /wiki/spaces/DQA/pages/2657909 (P1, P2, P3, P4)
- EXAMPLE: P2 -Check out the receipt emails are not sent to library users
- Pro tip: Indicate your level of priority in the summary - /wiki/spaces/DQA/pages/2657909 (P1, P2, P3, P4)
- Description:
- create a problem statement
- Indicate steps to reproduce
- what is expected to happen
- what is really happening
A stellar Jira ticket would contain:
• Library Name of who is impacted and what community environment the issue was recreated in
• The perceived impact/priority of the issue in the summary line
• Date/time(please include your time zone) the problem started
• What you expect to happen
• What actually happens
• Steps to replicate the problem
• Details! Screenshots!
Important: Also try do test(s) in one of the FOLIO reference environments like FOLIO Snapshot, or the latest FOLIO Bugfest environment, inorder to verify if this found issue is caused by a locally configuration problem, etc or this is a general FOLIO code issue.
Troubleshooting Tips and tricks:
• Which browser am I using? Google Chrome is the only officially supported browser for FOLIO.
• Can I reproduce the issue with another record?
• Does this also happen for my colleagues?
• Do I have sufficient permissions to perform this action?
• Are my app settings configured to support this action?
• Can I reproduce the issue in an incognito window?
• Can I reproduce the issue in a community reference environment on the same FOLIO version?
Looking under the hood
• Open FOLIO in Chrome
• Press F12 to open the browser’s Developer Tools
• Look at the Network and Console panes
• Any error messages?