I am never sure if it's a good idea to clump multiple similar reports into one ticket. If they are strongly linked and likely to be dealt with 'at the same time' then probably not a bad idea. However, the chances of us mere mortals having a clue as to who, when, and how any given resolution will be achieved it is likely better to do one ticket per product.
In my old job I know that I'd get a little miffed if a report came in with lots of stuff for me to do then and then also find it had stuff for someone else. Maybe a workflow manager picks up the ticket and sub-assigns the tasks to appropriate people, who knows? ;)
Comments
Redacted
I am never sure if it's a good idea to clump multiple similar reports into one ticket. If they are strongly linked and likely to be dealt with 'at the same time' then probably not a bad idea. However, the chances of us mere mortals having a clue as to who, when, and how any given resolution will be achieved it is likely better to do one ticket per product.
In my old job I know that I'd get a little miffed if a report came in with lots of stuff for me to do then and then also find it had stuff for someone else. Maybe a workflow manager picks up the ticket and sub-assigns the tasks to appropriate people, who knows? ;)