TAIT is transitioning to a new workflow for tracking iQ and Navigator requests. There are various reasons for this:
- The primary driver of this change is streamlining the bug reporting workflow. We have a connection between the Support Portal and our issue tracking system that allows for data gathered in one system to push to the other.
- Additionally, we now have one workflow for customer submitted bugs and for those that come from TAIT staff.
- Finally, we want to have a global community where TAIT staff and our end users can request new features and provide feedback.
If you're in a hurry:
How do I get a Support Portal account?
What is available on the Support Portal?
Knowledge base articles, iQ and Navigator release notes, manuals, and the community forum. Also, some organizations have information specific to them.
How do I view iQ/Navigator release notes on Zendesk?
Sign in to the portal and click on iQ Powered by Navigator or Navigator GUI. There, click on Release Notes.
Can I read the current help manual for Navigator on Zendesk?
Yes! Click here to start.
Can I read the current user manual for iQ on Zendesk?
Yes! Click here to start.
Where do I enter bugs?
Use this form.
Where do I enter feature requests?
Use the community topics.
How do I track bugs that I submitted?
For bugs you personally submitted, sign in to the portal and click on My Activities at the top right of the screen.
How do I track a feature request?
Sign into the community and find the appropriate post. You can reply to the posts, and upvote/downvote various feature requests.
Can anyone view my bugs and feature requests?
For bugs, only other members of your organization (if any) can see your bugs. For feature requests, the community is globally visible to everyone.
What happens after I enter a bug or feature in Zendesk?
For bugs, the software team will review the submission and decide the appropriate action. This may involve moving the submission into issue tracking system. Once you submit a bug you will receive an autoresponse via email to confirm receipt. As the item moves through software development lifecycle, you may be asked for more information or simply be informed when the issue is resolved.
For feature requests, the software team will review the posts. As requests work their way through the lifecycle, the status of the request (Planned, Not Planned, Completed, or Answered) will be updated and visible. Your feature request may be split off into a ticket to ease the transition into the issue tracking system.