RTC Time Duration attribute type - Limit of 1 year
Accepted answer
Thanks for the answer Ralph. These time duration fields were used to estimate large "chunks" of proposed changes to our product. These are not planned tasks. They will ultimately be decomposed into smaller planned items that will be "rolled up".
I think the only work around is to utilize integer values instead of time durations.
Thanks
2 other answers
Looking at it, I have to assume it is built into the presentation/attribute type. I don't think you can override this.
I don't know why you want to do this, but the idea with planning in RTC is also that you split work into smaller tasks where you actually can estimate something with a reasonable precision. RTC accumulates the effort in parent-child relationships within a plan.
From my experience any estimation bigger than a week is likely to be very imprecise. I have to confess though, I am generally pretty bad in effort estimation.
I don't know why you want to do this, but the idea with planning in RTC is also that you split work into smaller tasks where you actually can estimate something with a reasonable precision. RTC accumulates the effort in parent-child relationships within a plan.
From my experience any estimation bigger than a week is likely to be very imprecise. I have to confess though, I am generally pretty bad in effort estimation.