Dynamic variables mapping
G
Gina Dougherty
Feature Request: Dynamic Variables Mapping
Description:
Implement a feature that allows users to map dynamic variables to widget fields within Marker.io. This enhancement would enable the integration of various data points, such as the reporter's email or browser version, into the custom fields of existing integrations.
Key Benefits:
- Enhanced Data Accuracy:Automatically capture and map relevant data, reducing manual entry errors.
- Improved Workflow Efficiency:Streamline the reporting process by pre-filling custom fields with dynamic data.
- Customizable Integrations:Provide greater flexibility in how data is collected and utilized across different platforms and integrations.
Use Cases:
- Automatically map the reporter’s email to a designated custom field in project management tools.
- Capture browser version details and include them in bug reports within issue tracking systems.
- Store additional user-specific information directly into custom fields of integrations for better context and traceability.
Log In
Hakim Cassimally
It looks like this feature is marked "Planned", but I don't see it under the Roadmap dashboard.
I'm doing the 14 day trial to evaluate it, and we'd really want the feature to have parity with our existing Jira Issue Collector form, and for some enhancements:
* set custom labels depending on page metadata (using e.g. the Javascript API to set custom metadata https://help.marker.io/en/articles/5358889-custom-metadata
This would allow us to have issues automatically categorised and assigned in Jira, depending on the page that feedback was delivered for)
This feature would be useful for day-to-day feedback in the production environment.
set custom labels additionally based on
site* metadata. (For example for preview sites being developed for a specific feature, and targeted at a specific stakeholder. This feature on the other hand would improve our
development
workflow and stakeholder collaboration when working on new versions of documentation.As it stands, though we can use the Javascript API I linked to set custom metadata, this will only be synced in the Jira description, and not with Jira's own fields, meaning we can't take advantage of our existing workflows on that side.
Is there anything I've missed? Would be great to learn if there's a feature I've missed in the docs to do this (even as a workaround or beta test.)
James Avendano
I'm trying to create a dashboard in Jira for our Internal Customer teams, and the metadata is currently taking up a lot of space in the issue description that that data is currently mapped to by default.
Emile-Victor Portenart
Merged in a post:
Add the Title of the page as prefix
Equipe Projet
It could be useful to have in ASANA the title of the page where the visitor is as a prefix.
Example : If he is in the home page then make a report, the title of the report will be :
"Home Page > " + TITLE OF THE REPORT
Emile-Victor Portenart
Merged in a post:
Make browser environment optional
J
JH
It should be possible to disable "Record Browser environment" as this information is not necessary for all the use-cases and should be excluded from the created tickets.
Joe Scanlon
Merged in a post:
map marker.io values to as default values for form
BSR Materiality Platform
Please allow matching these field values as a default to custom fields from Jira integrations: Reported by, Source URL, and Issue details
Gary Gaspar
marked this post as
open
Gary Gaspar
marked this post as
planned