What is a destination?
A destination is a direct link to your projects inside your existing issue tracker.
Destinations allow you to collect bug reports directly into your team’s existing source of truth.
Unlike other bug reporting tools that force you to duplicate a new project, Marker.io let’s you connect your existing projects to the website you want to collect bug reports from.
One place. No duplicates.
Marker.io currently supports the following types of destinations
- Jira projects
- GitHub repositories
- Gitlab projects
- Bitbucket repositories
- Asana projects
- Trello boards
- Teamwork projects
- Monday.com boards
- Clubhouse projects
- Slack channels
Adding a destination
To add a new destination, go to your destinations page and click on Add Destinations. Select among one of our supported integrations and authenticate your account.
Once you've connected your integration account, select the tool in which your existing project lives and list the website on which you want to collect feedback from.
Managing a destination
Let’s look at the different parts that make up the inside of a destination
The first thing you need to do after adding a new destination is configuring your widget so that reporters can submit bug reports and feedback into your new destination. Go to the Widget tab and follow the instructions.
The Reports tab will be called differently based on your type of destination. A Jira project will have an issues tab, an Asana project will have a tasks tab and a Trello board will have a cards tab.
Under this tab, you will find a history of all reports sent via your destination’s widget.
Clients do have access to this tab, but with a limited view.
The report page
Click on any item in the reports list, and it will open a detailed view of your bug report inside your issue tracker.
The goal of the report page is to:
- External communication: Communicate with external reporters & clients who do not have access to the report inside your internal issue tracker like Jira, Trello and so on.
- Advanced technical data: Present some additional technical information to developers (eg: console logs)
- Log History: Keep a log of all reports sent in each destination via Marker.io
Tip: Do not think of the report page as a duplicate of your internal issue inside Marker.io. Rather, think of it as an external view of the same issue in your tools.
In the Users tab, you will find the list of Members and Clients who have access to this destination. By default all team members have access to all new destinations created. From this page, you can invite, add and remove Members and Clients.
Tip: To delete a user from your account (and stop paying it), you must go to your account settings, and delete the person from the Users menu here.
In the Settings tab, you can:
- Allow members to report via their own integration account
- Manage website domains
- Manage destination account
- Delete a destination
Troubleshooting a destination
Since destinations are always associated with a connected account from your integration, destinations can sometimes “break”.
For example, the Jira user who added the destination might get his Jira account deleted after leaving your company. Or your Trello board has been archived. But don’t worry, all admins will receive an email when that happens and it’s a very easy fix! Simply open your broken destination and we will guide you to fixing a destination.
Deleting a destination
To delete a destination, go this the Settings tab inside your destination and scroll down to the Delete destination section
Keep in mind that deleting a destination will delete everything. Although you will be able to add the same destination again, all previous settings will be reinitiated (script ID, report history, user configuration)
Can I use Marker.io without adding a destination?
Everything we do at Marker.io is to help teams and developers spend less time on bug reporting, bug tracking and bug fixing. Adding our own bug tracking tool in the mix will only slow down your process.
Tools like Jira, Trello, Asana and the like can do practically anything you can think of. This is where your team already makes work happen. It’s where all tasks get done.
That’s why at Marker.io we believe that new bug reports should only exist in 1 place: your team's existing tools.