Documentation Index
Fetch the complete documentation index at: https://docs.mavera.io/llms.txt
Use this file to discover all available pages before exploring further.
Scenario
Customer-reported bugs contain language revealing pain severity beyond a priority label. This job pulls issues labeled “bug” and “customer-reported”, creates user personas for different customer segments, then runs a Mavera Focus Group asking “How critical is this bug to your workflow?” — producing a severity map driven by synthetic customer voices. Flow: Linear GraphQL (issues with labels “bug” + “customer-reported”) → MaveraPOST /personas → POST /focus-groups → Poll for results
Code
Example Output
Error Handling
Label filter matching
Label filter matching
The
every filter requires ALL listed labels. If your workspace uses “Bug” vs “bug” or “customer_reported”, adjust values. Query issueLabels to discover exact names.Focus group polling timeout
Focus group polling timeout
Complex groups with 4 personas may take 60-90s. The loop allows 150s. Check the Mavera dashboard if
status never reaches “completed”.Priority field values
Priority field values
Linear priorities are integers: 0 (none), 1 (urgent), 2 (high), 3 (medium), 4 (low). Map them to text in your prompt if personas need clearer severity context.