Issues Tracker for both developers and end users [closed]
Closed 10 years ago.
How can I get an anonymous user to submit bugs on a private GitHub project?
Our company has a private GitHub repository for the project I’m working on. After a full summer of work, it looks like we’ll be launching this week (wheee!). However, I want to include a “submit a bug” link in the program that leads to a form somewhere where the user can fill out a form that becomes an issue for us on GitHub. Googling around hasn’t found any solution (or someone who has the same problem).
Bug severity classification issues
In a book I have, there is a following classification of defect:
schedule compliance and keeping technical supports and resolving issues
I am an entrepreneur of a small software developer company. The flagship product is developed by myself and my company grew up to 14 people. One of pride is that we’ve never have to be invested or loaned.
What makes for a good JIRA workflow with a software development team? [closed]
Closed 10 years ago.
How to use TFS as a query tracking system?
We already use tfs for managing defects in code etc, etc. We additionally need a way to “understand the domain & requirements of the products”. Normally, without tfs we exchange emails with the consultants and have the questions/queries answered. If it is a feature implementation we sometimes “find” conflicts in the implementation itself. And when that happens the userstory is modified and the enhancement/bug as per that is raised in TFS.
Is it a bug or a task when something doesn’t work, yet, in development process
We usually have this dilemma in our team. Sometimes, in order to implement a task or a story we find out that the system must be in a specific state. For example, a specific system configuration has to be made beforehand.
Responding to end users about bugs they found
I have an issue tracking system, but sometimes users report bugs directly to me in an email.
What to do when issue-tracker is down?
It has happened in our team that our issue-tracker is down. Happens about once a week now (yes, wow), and there’s not really much we can do to get it back up, since it’s hosted by our client in a different timezone. It sometimes takes several hours for it to be operative again.
What level/format of access should be given to a client to the issue tracking system?
So, I used to think that it would be a good idea to give the customer access to the issue tracking system, but now I’ve seen that it creates less than ideal situations, like: