Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

structure gantt chart - gantt sprint date is not editable

My gantt sprint start and end date is configured based on JIRA sprint date. The task that are in future sprint are not showing the correct date so I want to manually configure those sprint for the structure gantt chart. Can I accomplish that without disrupting the sprint date from JIRA.

 Jira Structure configuration.jpg

1 answer

2 votes

Hello @Viral_Vora ,

David from ALM Works here.  

At the moment, Structure.Gantt does not recognize future sprint dates, which is why you are seeing this behavior.  We do have a task in our backlog to address this.  I have added your request to the list of interested customers and will post an update here as soon as there is one to share.

As a workaround, we can do one of two things.  Both are similar in approach. They do require being on the most recent version of Structure (7.4) and Structure.Gantt (3.1)

1. Update the Scheduling Configuration:

This will be the better approach if seeing the Sprint name for Active Sprints at the top of the Gantt chart is not important. 

  • Enable 'Allow Manual Scheduling'
  • Disable 'Use sprints for manual scheduling'
  • For Start Date select Formula from the list of options and use sprint.startDate.last()
  • For Finish Date select Formula from the list of options and use sprint.finishdate.last()
  • Save > Save Settings

Screen Shot 2022-02-07 at 11.40.20 AM.png

All of your issues will now show the Start and Finish dates of the latest Sprint they were assigned to.

2. Utilize Slice Based Configuration:

This will be the better approach if seeing the Sprint name for Active Sprints at the top of the Gantt chart is important.  Please note that the the visualization for Future Sprints will not line up with the tasks.

In Scheduling Configuration -

  • Enable 'Allow Manual Scheduling"
  • Enable 'Use sprints for manual scheduling'
  • Disable 'Prefer sprints over manual start and finish dates'
  • Set Start & Finish Date to 'None'

In New Slice - 

  • Select JQL Option and use sprint in (futuresprints())
  • Add Section - Manual Scheduling
  • For Start and Finish Dates use the same formulas as the previous option
  • Disable 'Use sprints for manual scheduling'
  • Save > Save Settings

Screen Shot 2022-02-07 at 11.12.45 AM.png

Issues that are part of an active sprint will show under their sprint while issues assigned to future sprints will show in the correct spot on the chart, but not under their assigned sprint.

To make the visualization here better, you can Add another Section for 'Appearance' and pick a new color for issues assigned to a future sprint.

Please let me know if this helps!  Please also feel free to contact our support team for additional assistance via email or customer portal!



Please confirm if this issue is fixed in the latest release of Structure Gantt (Cloud) as on today.


Like Dave Rosenlund _Tempo_ likes this

Hello @Viral_Vora ,

Just following up to let you know that Structure.Gantt now supports Future Sprint dates!

@Santhosh R Bhat this is true for Cloud as well.

Please let us know if you have any questions.


Like Dave Rosenlund _Tempo_ likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events