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?