The best way, I think, is to assign someone to review all incoming issues, then make them "real" bugs assignable to your development team. Obviously, the users are unable to track how their issue progresses.Since the users don't search for existing issues, you will likely get many duplicates.Even more, since the users aren't registered, it is hard to retrieve missing info LinkedIn - Team Leader - Mobile Development (Flutter and native) - Web Development (Flutter) - BaaS (Firebase), Parse Server - Unit test/ UI test/ Integration test - Training 12-year mobile/web apps.It may lack Environment, Steps To Reproduce, Expected, or Actual Result, attached logs or screenshots They simply can't provide with quality bug report that could be directly processed. Often, your users are not technical people.However, opening a direct way to gather feedback has its disadvantages, and you have to define rules on how to process the feedback efficiently: Yes, the captured feedback goes straight into JIRA in the project you specify, so your team can act on that feedback. If you develop web-applications or web sites, the JIRA Issue Collector is the best way to turn your customers' and users' feedback and problems directly into JIRA issues, all without requiring a JIRA login. Need to capture feedback on your website or web application? Want to make it easy for end users to directly create bugs so your developers can act on them? Each quarter our research team identifies companies that have purchases Atlassian JIRA for Project Portfolio Management from public (Press Releases, Customer. You should take a look at Jira Issue Collector.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |