Project

General

Profile

Making sure everyone knows if someone is waiting for a response from them

Added by Attila Szeremi over 10 years ago

This has always been an issue in other project tracking software I have been using.
When there are many tickets out there, it gets hard to track where feedback is required from you. Even if a ticket is set to "Feedback", it doesn't necessarily mean that it is you the feedback is needed from, meaning having a bunch of "Feedback" tickets aren't very helpful either.

I remember in an old project, what we used to do was after every reply we make in a ticket to someone (and want the other person to know about it and respond), for every single comment, we reassigned the ticket to the person we want a new response from. Even development related tickets that are assigned to us by clients we reassigned back to the client when communicating with each other, not because we want to assign the development task to the client who obviously can't program, but so that it would appear among the "assigned to me" list on their end and that they would have much better knowledge of what tickets require their feedback/responses.

Is what I've described considered good practice? If not, I would like to ask your opinions on a better style of making sure everyone knows where responses are expected of them.


Replies (1)

RE: Making sure everyone knows if someone is waiting for a response from them - Added by Jan Niggemann (redmine.org team member) over 10 years ago

Attila Szeremi wrote:

This has always been an issue in other project tracking software I have been using.
When there are many tickets out there, it gets hard to track where feedback is required from you.

When someone requires your feedback, then he / she should assign the issue ticket to you.
If the ticket is required to keep its currents assignment, then create a sub-issue and assign that to the person you need feedback from.

Is what I've described considered good practice? If not, I would like to ask your opinions on a better style of making sure everyone knows where responses are expected of them.

See above :-)

    (1-1/1)