Guide to Triage Your Experience Before Submitting a Bug Report
Last Updated on August 21, 2024 | 2 min read
Step 1: Check the Documentation
Review the user guide or help center content related to the feature you’re using. Ensure you are following the correct steps as outlined in the documentation.
- NIVOMAX IETP / IETM Viewer User Guide
- NIVOMAX IETP / IETM Self Serve Portal User Guide
- NIVOMAX IETP / IETM Builder User Guide
- NIVOMAX IETP / IETM Sales Center User Guide
Step 2: Replicate the Issue
Try to repeat the actions that led to the unexpected behavior. If the issue is consistent and occurs every time you perform the same steps, it may be a bug.
Step 3: Verify Your Environment
- Check if your software is up to date. Ensure you have installed the latest patches or updates.
- Make sure your system meets the minimum requirements for the software.
- Confirm that your network connection is stable as the software relies on online features.
Step 4: Consider Other Factors
Think about any recent changes you made to your system or software configuration. If the issue started after a change, it might be related to that adjustment.
- Anti-Virus Policy Changes: Ensure your anti-virus software hasn’t quarantined or blocked any files related to NIVOMAX. Check exception lists, and confirm with your IT team whether there have been recent changes in the anti-virus policy.
- Network Access Policy Changes: Verify that necessary ports for NIVOMAX communication are not being blocked by updated firewall rules. Check VPN or proxy settings, and confirm that there haven’t been changes in network policies or ACLs.
- License Validity and Access to Libraries: If you are having issues accessing specific Libraries, contact your Data License Admin to confirm whether your license is still active. If your access has been revoked, you will lose access to those Libraries.
Step 5: Consult Known Issues
Check the help center for any known issues that might match your experience. If your issue is listed, follow the suggested workaround or resolution.
Step 6: Get a Second Opinion
If possible, ask a colleague or another user to try the same steps. If they experience the same issue, it’s more likely to be a bug.
Step 7: Prepare Your Report
If, after following these steps, you believe you’ve found a bug, gather as much information as possible.
- Describe the steps you took.
- Note the version of the software and your operating environment.
- Include any relevant screenshots or error messages.