Thank you for the feedback. Please, see my update in the comments!
It is possible to manually define both Start and Finish dates and Effort still will be calculated by these dates at the moment, but we're working on a "fixed effort" mode which as far as I understand is something you're interested in. I.e. Effort will always remain the same but you will be able to adjust start and end dates without affecting it.
Concerning Epics and their effort. This is possible to do with a Script Runner and not with Structure.Gantt because currently it is out of the scope of our plugin. That might change later.
Thanks again for your interest and feedback!
> When I have an epic in Structure and I change the duration in Gantt (moving start and end of the stripe) than the duration value is inserted in the Original Estimation Field (which is in my opinion completely wrong).
That's not true. The value that is being inserted into Original Estimate is Effort that was calculated based on the new task duration. You can check this by clicking on a task and changing Max. Units (you can read about Maximum Units here https://wiki.almworks.com/display/gantt/Gantt+Chart+Elements) to, for example, 0.5, as a result your Epic durations should double but Original Estimate should remain intact. Then you can try to resize your Epic to a half and see how Original estimate is changed to a half of its previous value. So, actually, Original Estimate indeed is Effort and not the Duration.
> If I add some stories below the epic than the estimated effort is added to the epic effort (which was the duration in fact). The duration (stripe length) in the Gantt is updated to the first and last story below (which is correct) but the Original Estimation Field remains with the wrong value (which is also strange)
This is because your Epic becomes a Group (a black bracket covering its children), i.e. a simple grouping of issues. You still see it is an Epic in the WBS, right, but Gantt treats it differently and ignores task properties such as Original Estimate, etc. Groups aren't tasks and doesn't have any Effort specified but only a Duration which is calculated based on their children schedules. You can not change the duration of a group by drag and drop, nor its Original Estimate or Manual Start is taken into account.
> I expect: Duration is a separate field than Originally Estimation. The length of the stripe in Gantt is connected to a duration field. The effort (Original Estimation) can be set independent.
That's exactly how it works now, except that there is no Duration field which is calculated dynamically based on Effort, Calendar, Maximum Units and assigned Resource.
> When I define stories below (an Epic) the duration is updated to the stories. Why is it not possible to update the epic Original Estimation field to the stories too (Epic Effort is set to 0 and only shows the summary of the stories, otherwise the effort is estimated twice)?
It is not possible to do in Gantt chart directly since groups has no Effort as I mentioned earlier, but you can do it with a ScriptRunner script for example. Moreover, it seems like your issue is not directly related to Gantt chart itself since Original Estimate of the Epic will not be visible in the chart nor be used by it anyway.
> Structure is great idea, I really would like to use it. It would really supports the WBS creation. But exactly the actual behaviour (connection between duration and effort) makes it unusable for a WBS creation.
> The Parents are defined from the beginning to get a duration idea for the final project closer an rough effort estimated to get a cost idea. Especially in agile environment, during the whole project lifetime I brake down Parent issues. This two values (duration and effort) should be handled separate and independent over all issues.
I understand your problem but it this is the way our gantt currently works - we are trying to keep it flexible enough so that users can use it in different scenarios, but unfortunately it’s not possible to make it work in all situations. You can still achive desired behavior (of updating epics Original Estimate) by extending Jira and using ScriptRunner.
Thank you for the feedback!
Actually, Duration is separated from the Effort: there is Work (Effort) and Duration that you can inspect by clicking any task or group (for groups Duration only is shown).
Can you elaborate more on your particular setup so I can better understand your case?
Thank you for a suggestion and a feedback!
Can you explain a little more about "hash marks"? Are you talking about visualizing milestones in the group row if the group itself is collapsed and milestones aren't visible, right?
Thank you for your answers!
Thank for your response! I have more questions for you, if you don't mind :)
So, you prefer to schedule these several-hours of work tasks manually? That's because these tasks are independent of others or there is another reason? I mean, I'm trying to understand why are you going so deep and plan your tasks at hours zoom level.
About the readiness. I'm trying to figure out how we can improve UX in your case (and probably in some similar cases) at the moment. That's probably can be done without even changing the timeline, but I need to understand your process in more detail to make any assumptions. Hours zoom level was originally designed to be clear of time distortions, missing hour, etc, and our thought was that our users will plan at higher levels and use hours zoom for exact time validation mostly.
Thank you for the response!
I got an idea of how your tasks are organized, but can you tell me more about overall process and particularly about:
* Is it true that most of your tasks takes several hours of work?
* Are you planning your tasks within a one single timezone?
* Do you use other zoom levels except 1 hour zoom?
To better understand your needs I would like to ask you several questions:
* How small are your tasks?
* Are you planning all your tasks within a one single timezone?
* Do you use other zoom levels (days, months)?
Thank you, and thank you for the feedback!
Please see my comment.
As far as I understand, you want to be able to view (as a columns) and sync back to Jira start and finish dates of auto-scheduled tasks, right?
This feature is planned and will be available in one of the upcoming releases, please see our Roadmap for the full list of planned features: https://wiki.almworks.com/pages/viewpage.action?pageId=48267817
Thank you for the feedback!
Paul, please see my comment
Thank you for the suggestion! We're working on the visualization of sprints and fix versions at the timeline (simple visual marks) at the moment and have plans to support fix versions as milestones sometime later.
Our idea was to automatically represent Fix Versions as milestones for result of the "Group by Fix Version/s" automation since by nature milestones should have associated structure item (either an issue or a folder) and currently it is the only way to see Fix Versions as a separate items in the structure.
Does it sounds good for you?
Thank you for a suggestion! Can I ask whatever you expect this offset to be specified per task or for a dependency type, or for some specific issue types, for example?