History | Log In     View a printable version of the current page. Get help!  
Issue Details [XML]

Key: CHD-812
Type: New Feature New Feature
Status: Open Open
Assignee: Unassigned
Reporter: Joe Geck
Votes: 3
Watchers: 1
Operations

Clone this issue
If you were logged in you would be able to see more operations.
Cerberus Helpdesk

[Reports] Response Time Report - Time worked colourised based on whether Response time SLA achieved or not.

Created: 18/Aug/08 07:11 PM   Updated: 02/Aug/09 02:02 PM
Fix Version/s: We Have the Technology

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Issue Links:
Related To
 
This issue is related to:
CHD-811 [Reports] Service Level Report - Show... Open
CHD-959 [Reports] Average response time repor... Open

Value: 2 - Significant Value


 Description   
Summary:
http://www.cerb4.com/forums/showpost.php?p=5501&postcount=6

Report showing whether response time SLA was achieved or not.
As the poster mentioned this may go hand-to-hand with average response time. Perhaps merged together?

[[quote]]
Response Time Report - Shows average response and Time worked colourised based on whether Response time SLA achieved or not.
[[/quote]]


 All   Comments   Work Log   Change History      Sort Order:
Comment by Joe Geck [18/Aug/08 07:26 PM]
CHD-811/812:

These two ideas seem like they would naturally be implemented together if we decided to tackle them. However I chose to make them separate issues because I can easily see these being two singular ideas that don't necessarily need to be coded in tandem.

As Jeff has mentioned before, it's much easier to close one bug/request/task as finished when there isn't a mutated issue that includes similar but multiple ideas that we may not implement.

Note: They are linked together of course since they are so similar.

Comment by Joe Geck [25/Nov/08 02:07 AM]
Similar need or desired outcome for "average response time" reports in CHD-811, CHD-812, and CHD-959.

All are filed separately to avoid mutated requests, but if any feature was actually implemented on our side it would probably encompass all these ideas. Very similar to how the 'home' feature resolved multiple JIRA requests.