Platform Bug & Happiness Submission

Depending on your familiarity with the Test IO platform's expected behavior, sometimes it's difficult to know if your idea is a Happiness request or bug. Try to ask a colleague for clarification and if you're still not sure, just use your best judgement when submitting. The Happiness process is meant to address smaller scope feature requests from all departments. If there is any doubt about ticket scope, please don't worry about it. Just submit the request and the Product team will figure it out. There are no bad Happiness Requests :)

Can't find your email?
Your role
Choose the test IO user group (interface) that your submission/request applies to.
If your request applies to more than 1 user group, select the most affected group.
Choose the testing model that your submission/request applies to.
Components (optional)
If your request doesn't pertain to one of these components, skip this question.

Legend:
• Notifications: related to content or channel of stakeholder notifications
• Data: related to tracking of data
• Logic: systematic changes to tester invitations, validations, etc.
• ThirdPartyTool: test IO tools that integrate with a test IO Interface
• Devices: changes to device requirements, device categories, etc.
• Export: related to mapping logic, exporting of data, etc.
I am submitting a
This answer becomes the Jira issue title so keep it short. (max length 256 characters)