You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We are using Structure Gantt for our scheduling.
We currently have tasks that multiple people can log hours into, meaning the duration of the ticket shouldn't be based off "logged hours" but instead just the original estimate.
When two people have logged hours on a task, it elongates the task's duration in the Gantt chart. This is incorrect as their hours are done at the same time.
If I try to manually set the task's scheduling back to original duration estimate, it says:
"Cannot change estimate - Updated Work Estimate cannot be less than Time Spent."
How can I set this so that it only uses the Original Estimate rather than Time Spent?
Is there a better way to use one task with multiple assignees?
In your current setup a workaround can be applied for only using Original Estimate for Duration without the consideration of Time Spent. Here is how it can be done:
Please note that in case of using a formula, it is not going to be possible to change Duration on a chart by resizing a task's bar, it will be read-only (but if you change Original Estimate in Jira, Duration on a chart will be readjusted accordingly).
And as for using a multiple assignees for issues - we would suggest splitting issues into several sub-issues, each sub-issue assigned to one user. In this case, there would be no need for a workaround with formula and a sub-issues’s duration on a chart will stay equal to its Original Estimate, regardless of logged work. And if you also select the ‘Treat parent issues as groups’ option in the configuration (the ’Scheduling’ tab as well), it won’t need to have its own duration - it will be taken from its sub-issues’ duration.
@Stepan Kholodov _ALM Works_ I am interested in possibly using Structure for project planning based on duration, however, in my case, duration and effort are NOT the same. I need to plan and track duration separately from time tracking, which is used to track billable time.
I have a separate thread set up, but went looking in the community to see if this has been done. This is the closest I could find.
David from ALM Works here. Structure.Gantt allows you to specify what duration, start, end, etc values you want to use to visually represent your tasks on the chart.
If you would like to discuss your use case, and options available through Structure.Gantt, in more detail please feel free to contact us directly at email@example.com or through our customer portal support.almworks.com
We look forward to hearing from you!