Review / Triage feedback in Marker.io
under review
Gary Gaspar
Review and triage feedback into Marker.io before sending it into integration to avoid spam or poorly defined issues. It would be like a feedback buffer.
We have a workaround available for this. I would love to get your feedback:
Log In
C
Carl McCauley
The workaround in this article is not a very effective or useable workaround.
- It requires creating a duplicate project in Jira and then keeping that triage project in sync with the main project in Jira (configuration changes, etc). This is very complicated and difficult, especially for large projects in Jira that change periodically (new fields, etc).
- The triaging is typically done by the marker io user. For instance, recording all found issues while testing for a demo or customer configuration. Typically, the end user captures all the issues quickly while prepping for a demo. Then they come back and add details to each ticket, decide if things are a problem or not, etc. They then move those tickets to devlopment. With the proposed workaround, the end user needs to go into Jira and move those tickets over and close out their other tickets. That's not easy for a non-jira user.
- The issue in jira that is moved over is now separate from the Marker system. So the end user (like person for demo) doesn't know the status of the issue being resolved by development.
Gary Gaspar
under review
Gary Gaspar
open
Gary Gaspar
under review
Joe Scanlon
We have a temporary solution for reviewing feedback
You can find the details here:
.
Your feedback on this workaround would be greatly appreciated.🙏