| Reporter |
Jim Parker (jparkerbgs)
|
|---|---|
| Created | Mar 13, 2013 12:53:26 PM |
| Updated | Mar 13, 2013 2:52:23 PM |
| Priority | Normal |
| Type | Bug |
| State | Open |
| Assignee | Pavel Nikolaev (pasha) |
| Subsystem | Time Tracking |
| Fix versions | No Fix versions |
| Fixed in builds | No Fixed in build |
| Affected versions | 4.1.3 |
| Browser | Any Browser |
| OS | Any OS |
| Verified in build | Not verified |
| Verified by | Nobody |
| Reviewed by | No reviewed by |
| Severity | Routine |
We're looking for a simple way to work around the lack of support for determining per-user work remaining in a sprint, by attempting to use the information exported via CSV. While the output is close, it's not quite usable directly.
What steps will reproduce the problem?
1. Add some estimations for some tasks
2. Add some work to those tasks
3. Export as CSV
What is the expected result?
That the estimation column just shows time remaining, or that another column was present alongside Estimation and timeSpent to represent 'timeRemaining' (just an integer in hours).
What happens instead?
We get <span title=x left out of y" class="ttrack-progress-ico" style="background-position: 0 1px"></span>y. Where y can be a combination of nWnDnHnM (weeks, days, hours, minutes)
What steps will reproduce the problem?
1. Add some estimations for some tasks
2. Add some work to those tasks
3. Export as CSV
What is the expected result?
That the estimation column just shows time remaining, or that another column was present alongside Estimation and timeSpent to represent 'timeRemaining' (just an integer in hours).
What happens instead?
We get <span title=x left out of y" class="ttrack-progress-ico" style="background-position: 0 1px"></span>y. Where y can be a combination of nWnDnHnM (weeks, days, hours, minutes)