Is there a way to switch off time recalculation in RTC 2.0 ?
When entering estimates or time values for tasks, as soon as the value (specified in hours) gets higher than one day, it is automatically recalculated to 8h=1d, and so forth. I hated this since RTC 1.0 because this recalculation does not make sense at all if you consider the time to be ideal time.
In ideal time 12 hours are 12 hours. It does not make sense to recalculate that to 1d4h.
12h elapsed time are 1d4h indeed.
12h ideal time are 12h rather.
Is there a way to switch this annoying recalculation off?
Does someone know more details? Any help or comment is really appreciated.
In ideal time 12 hours are 12 hours. It does not make sense to recalculate that to 1d4h.
12h elapsed time are 1d4h indeed.
12h ideal time are 12h rather.
Is there a way to switch this annoying recalculation off?
Does someone know more details? Any help or comment is really appreciated.
9 answers
starz wrote:
Is there a way to switch this annoying recalculation off?
No. Feel free to log an enhancement request to add hours based
presentations for durations.
--
Cheers, Johannes
Agile Planning Team
There may be a more general enhancement here to configure the way time is displayed in each field. For example, many organisations plan using an FTE unit rather than days or hours or other duration. It can all be stored in the same way, just need to reformat the display element.
anthony
There may be a more general enhancement here to configure the way time is displayed in each field. For example, many organisations plan using an FTE unit rather than days or hours or other duration. It can all be stored in the same way, just need to reformat the display element.
anthony
I think the feature provided for RTC 2.0 to completely customize the units for stories addresses many needs. Would be interesting to know if this solves what you mentioned by FTE unit?
For tasks, I would suggest to stay with hours. It would be a good start to simply make the recalculation optional.
Anuerin added a link to a corresponding item. Would that be the right place to track this function or should an additional one be opened?
- Thomas
There may be a more general enhancement here to configure the way time is displayed in each field. For example, many organisations plan using an FTE unit rather than days or hours or other duration. It can all be stored in the same way, just need to reformat the display element.
anthony
I think the feature provided for RTC 2.0 to completely customize the units for stories addresses many needs. Would be interesting to know if this solves what you mentioned by FTE unit?
For tasks, I would suggest to stay with hours. It would be a good start to simply make the recalculation optional.
Anuerin added a link to a corresponding item. Would that be the right place to track this function or should an additional one be opened?
- Thomas
Let me create a new work item and then reference to Enhancement 60807.
Perhaps we need a new relationship between work items - "somewhat related" :-) (only joking)
anthony
starz wrote:
Please no a new request as the one referenced is about the work item
export. Internally dates are always stored in milliseconds, so what we
need a simply a new representation for it.
--
Cheers, Johannes
Agile Planning Team
Anuerin added a link to a corresponding item. Would that be the right
place to track this function or should an additional one be opened?
Please no a new request as the one referenced is about the work item
export. Internally dates are always stored in milliseconds, so what we
need a simply a new representation for it.
--
Cheers, Johannes
Agile Planning Team