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?
It is indeed impossible to use same link type for several dependencies since doing something like this will produce a cycle. For example, if issue "A" blocks issue "B", then issue "B" is blocked by issue "A" (note two opposite links between "A" and "B"), so in gantt chart we'll have two dependencies:
"A"'s finish to "B"'s start and "B"s start to "A"s finish
So, these two tasks "A" and "B" will depend on each other and Structure.Gantt will not be able to tell which dependency should be respected and which one should be thrown away, so both dependencies will be marked as invalid and linked tasks will not be scheduled correctly (please, also note that Finish-to-Start dependency isn't an opposite of Start-to-Finish one).
Could you please tell me more about what you're trying to achieve?
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?
Thanks for your suggestion! We indeed have some plans for exporting Gantt chart. Probably a chart itself as an initial implementation with a WBS alongside as an improvement later.
Josh, it is planned for one of our upcoming releases. You can see the roadmap here https://wiki.almworks.com/display/ganttmaster/Structure.Gantt+Roadmap