Marker.io automatically captures a rich set of technical data with every report. This includes browser, operating system, zoom level, screen size, console logs, network logs, source URL, reporter details and more. You can also add your own custom metadata to make the reports even more precise. Many teams would like to map this data into specific fields in their project management tools.
Native dynamic field mapping is something we are considering for future updates. You can vote and comment on the feature request here:
https://feedback.marker.io/feature-request/p/dynamic-variables-mapping
The good news is that you can already achieve much of this today by using automation inside tools like Jira. This guide walks you through how to extract Marker.io data from the description field and map it into your own Jira fields.
1. Decide which data you want to capture
For this example, we will collect and map the following:
Browser
OS
Website environment such as Live or Staging
Browser and OS are automatically captured by Marker.io.
For the environment, you can use the URL or define custom metadata.
2. Add or verify Jira fields
Before mapping data, create the corresponding fields inside Jira, such as:
Browser (short text field)
OS (short text field)
Environment (short text field)
Short text fields are usually best for these values.
3. Capture environment data with custom metadata
If your staging or production environment can be inferred from the URL, you can automatically detect it with custom metadata. For example, if your staging URLs contain the word "staging", add the following snippet to your Marker.io installation:
customData: {
mEnvironment: window.location.href.toLowerCase().includes("staging")
? "Staging"
: "Live",
}Learn more about custom metadata here:
https://help.marker.io/en/articles/5358889-custom-metadata
Once this is added, all Marker.io reports will include the environment along with the browser and OS.
4. Inspect the description field sent to Jira
Marker.io sends all technical data to your integration inside the description field.
To map values, you first need to see how they appear in Jira.
How to inspect the description via Jira Automation
Go to Project settings
Open Automation
Create a new rule
Add an action Log action with the content:
Description field is {{issue.fields.description}}Trigger the rule on issue creation and submit a test report from Marker.io
The log output will show something similar to this unstructured data example:
*Reported by:* Mark Member *Source URL:* [https://markerdemo.com/|https://markerdemo.com/] *Marker.io Issue type:* Bug *Issue details:* [Open in Marker.io|https://app.marker.io/i/6932d993a40b048b59a39026?advanced=1] — #JIR-19 *Console:* [View console logs|https://app.marker.io/i/6932d993a40b048b59a39026?advanced=1&activePane=console] *Network:* [View network logs|https://app.marker.io/i/6932d993a40b048b59a39026?advanced=1&activePane=network] ||Device type|desktop| ||Browser|Chrome 143.0.0.0| ||Screen Size|1920 x 1080| ||OS|OS X 15.6.1| ||Viewport Size|1920 x 907| ||Zoom Level|100%| ||Pixel Ratio|2x| ---- *Custom metadata* mEnvironment: Live
This tells us exactly how the values appear, which allows us to extract them using regex.
5. Prepare your regex patterns
Below are example smart value expressions that extract key variables from the description:
Browser
{{issue.fields.description.match(".*Browser[|]([^|]+).*")}}OS
{{issue.fields.description.match(".*OS[|]([^|]+).*")}}Environment
{{issue.fields.description.match("mEnvironment:\\s*([^\\n]+)")}}
Tip: You can paste your full description output into any AI tool and ask it to generate regex patterns for the values you need.
6. Create the Jira automation rule
Now that the fields exist and you have working regex patterns, create the mapping rule.
Go to Automation
Create a rule from scratch
When: Issue created
Add component: Create variable
Name:
theBrowserValue:
{{issue.fields.description.match(".*Browser[|]([^|]+).*")}}
Add component: Edit issue
Set the Browser field to
{{theBrowser}}
Repeat this for OS and Environment using your corresponding variables.
Turn on your rule and submit a new Marker.io report to test it.
If everything is set up correctly, you will now see your Jira fields automatically populated with the technical data captured by Marker.io.
7. Additional tips
If you need any data that Marker.io does not capture automatically, custom metadata is the best solution. Feel free to contact us if you need help setting it up.
Once you can see a value inside the description field, you can almost always map it to a native integration field using your tool's automation features.