Historically, fixversion was the field used by GH for sprints.
Since they contained start and end date metadata it was possible to populate start and end date for a user story in a fixversion based on the metadata of that fixversion.
However, in the new scheme were "sprints" are used, it is not possible (as far as I know) to set start and end date for a sprint before the sprint is actually started making it far less useful for project-planning purposes.
Is this functionality still supported in this new scheme, and if so - how?
You can still use fixversions, but my addon supports the newer sprint and rank customfields as well. As soon as you assign an issue to a sprint, all related issues of that sprint will be re-scheduled.
But you are right, that assigning start/end date of a sprint is a bit anoying to be done by "start sprint" and not earlier. I will think about it, if a workaround is possible.
Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs