Search code examples
issue-tracking

Who is responsible to look into client reported issues


In our organisation we deliver products to different product lines depending on the requirements. in short the same application is customised according to customer requirements and delivered. After deploying the application sometimes we got some issues logged by client.

My question comes here. who is responsible to look into the issues and solve it

  • Programmers
  • Testers

Management is asking Testers to have a look into the issues and solve them. But the testers don't have the chance to look into the code. is it feasible to ask the testers to go for the issue resolution and end up wasting time doing nothing thus delaying the solution to the customers.


Solution

  • I would normally expect management to look through the issues every so often (say, every week), and allocate depending on schedules, severity, forthcoming releases etc. Some questions are:

    1. is it an issue a bug, a feature request etc.?
    2. does it prevent your client from working with your tool ?
    3. is it impacted by forthcoming work (e.g. will a new feature remove the feature causing the issue) ?

    I don't believe you can resolve these issues in isolation. It requires project managers etc. with awareness of project direction and programmers with awareness of the codebase to work together to determine how/when issues should be addressed, and their impact on other work streams.