Forms are one of the most powerful features in Marker.io. They work a bit differently as one would expect, as they are deeply integrated with your favorite project management tool.
All fields inside your forms are reflected from existing projects inside your project management tools. For example, if you use a “Sprint” field inside Jira, an Asana custom field or a Github “Milestone” field, these will be available inside your forms.
All field values from your issue tracker are synced each time your forms are loaded. For example, if you add a new colleague inside Jira, Asana or Github, this person will instantly be available inside the assignee field, without any update needed in Marker.io
Because your fields inside your forms are the same fields as in your issue tracker, some will be more sensitive than others which is why you can hide any field you want to your reporters.
Internal Testing + External feedback
Not all reporters have the same need. An internal QA will need to add more context every time they report an issue, while a client or an external user will only need access to fill out a description and maybe a label or a priority. Using the same widget, your can display a guest form for your non-tech stakeholders while internal members will be able to fill out your team form with more fields.
You can learn more about how the Guest role works here.
🙌 Help: I’m not seeing the correct form!
If you’re a Member and you’re seeing the Guest form, make sure to:
- Log into your Marker.io account in the background
- Make sure you have access to the destination
- Refresh your website with the widget
If you’re still not seeing the right form, fill out your bug report via the guest form and when asked to provide your email address, enter the one used for your Marker.io member account. When submitting, Marker.io will recognise the email address and ask you to log in.
Also make sure your cookies settings in your browser allow cross domain linking by following this guide