Duration getting updated to inaccurate number when the tasks are assigned to an iteration | Community
Skip to main content
June 3, 2025
Solved

Duration getting updated to inaccurate number when the tasks are assigned to an iteration

  • June 3, 2025
  • 2 replies
  • 282 views

Hi All, 

I have a project created with a set of tasks. I had updated duration, planned hours and assigned the tasks to an agile team. Once the tasks were assigned to the agile team, those tasks were showing up in the team's backlog. When I added few tasks from the backlog to one of the iterations, the duration of the tasks in the tasks list in the Project page got updated to very large numbers (57 days) whereas the original duration i had updated is very less ( 1 Day). Not sure why this is happening. How to retain the original duration of the task after it is getting assigned to an iteration.

 

Please provide your inputs. Thanks in advance.

Best answer by KellieGardner

what is the duration type of the tasks in the project? If it's calculated, then that could be your culprit.

 

Calculated Work Duration Type 

Work Required (Planned Hours) = (Duration of the task in hours) x (The number of resources assigned to the task)

 

 

Overview of Task Duration and Duration Type | Adobe Workfront

2 replies

KellieGardner
Community Advisor
KellieGardnerCommunity AdvisorAccepted solution
Community Advisor
June 12, 2025

what is the duration type of the tasks in the project? If it's calculated, then that could be your culprit.

 

Calculated Work Duration Type 

Work Required (Planned Hours) = (Duration of the task in hours) x (The number of resources assigned to the task)

 

 

Overview of Task Duration and Duration Type | Adobe Workfront

kautuk_sahni
Community Manager
Community Manager
July 29, 2025

@balajich1 Just checking in — were you able to resolve your issue?
We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!

Kautuk Sahni