Issue Types on Forms
in progress
Ken Hoffman
Limit Issue Types for Members on Marker.io
Description:
Would like to request the ability to limit and customize the issue types available for members when filling out forms on Marker.io. Currently, this feature is available for guest forms, but not for member forms. The main goal is to prevent errors and ensure the accuracy of data by only displaying relevant issue types.
Use Case:
- Prevents miscategorization of feedback by restricting irrelevant issue types.
- Allows teams to separate feedback into appropriate categories (e.g., Bugs, Peer Reviews) for better data accuracy.
- Enables teams to customize the issue types shown to members based on their specific workflow needs, such as focusing only on QA-relevant types or limiting to specific categories like "Improvement", "Bug", and "New Feature".
Benefits:
- Reduces errors and ensures clean data entry.
- Customizes the user experience to better fit the team's workflow.
- Enhances data accuracy by limiting issue types to only those relevant.
Log In
Gary Gaspar
Merged in a post:
JIRA - Member - Choose Default Issue Type
D
David Paquet Pitts
For Members who are connected with JIRA, the default Type is Task.
For feedback coming from Marker, we would like to specify the default type so that our internal QA analyst does not have to change it manually on each new feedback created.
Gary Gaspar
Merged in a post:
Allow reporters to select the type of feedback they wish to submit
K
Kyle Rumble
For example reporters might want to report: bugs, or feedback, or content updates, or design revamps. Allow reporters to select the type of feedback they wish to provide and display a specific form based on that feedback
Create multiple widget forms by project. For example, Send "bugs" into Jira and "content ideas" into Asana
While we wait for this feature, we currently have some work arounds and ideas here:
Gary Gaspar
Gary Gaspar
in progress
Joe Scanlon
Merged in a post:
Improve Forms configuration capabilities
Mathieu Delafosse
Allow me to share 2 simple ideas :
First, programmatically by adding a method in the MarkerSDK to set the form content.
MarkerSDK.setCustomDescription(
Encountered a bug ? Explain what happened.
);or
MarkerSDK.setCustomFormContent({ type: 'Bug', description:
Encountered a bug ? Explain what happened.
});or
MarkerSDK.capture({ mode: 'fullscreen', customDescription:
Encountered a bug ? Explain what happened.
, customType: Bug
})============
Otherwise, in the Widget configuration, by allowing the Form content to match the "Type" of feedback.
For example, if you choose "Type: Bug" you use "
Encountered a bug ? Explain what happened.
" as description.But if you chose "Type: Improvement", you use "
Want to help us improve ? Please share your feature request
"Thanks!
Gary Gaspar
planned
Gary Gaspar
under review
Mike Rand
This is becoming a bigger issue for my team. We want to be able to separate feedback into different ADO objects (e.g., Bugs, Peer Review, etc.). What happens now is that when a Peer Review is conducted and feedback is entered the form defaults to "Bug", so we aren't getting clean data.
L
Leonard Burton
Definitely would love to have this. I just want to use it for bugs at the moment so there's some inevitable step where I have to update the issue types in JIRA. Even if we use more types later, it's going to be less than we want exposed to even our members.
Load More
→