Our team was just "strongly encouraged" to upgrade to greenhopper 6.
I'm looking for a way to be able to export stories that are set up in a sprint in the new "boards". In the classic board view you could export stories, and when changing the "fix version" of the story to the desired "release" it was very easy to organize stories into sprints.
The new drag and drop features of the new boards is cool, but I can no longer get stories/issues, organized by sprint, with all their associated data exported to generate the reports and weekly status updates required by my managers.
I would rather not go back to the "classic" boards if I don't have to, but if I can't get issue data to export grouped by sprint I think that's the only option I can see.
Anyone have thoughts?
Just go to the Sprint Report, use the 'View in Issue Navigator' link then 'Export to Excel'.
Alternatively you can just use JQL like "filter = <board filter name> and sprint in openSprints()" to capture all stories in the open sprint on a particular board.
I have a similar problem, but I actually want to capture future sprints and not just the working sprint, for future planning and compliance reasons.
Namely, I want to be able to take a "snapshot" of our planning board. Is there any way to do this? I noticed that when I download an CSV of all our stories, the "sprint" field is only populated if the story is in the working sprint, or a past sprint. Why is that?
Hey Shaun, thanks for responding. This will get me what I need for now, just a little extra sorting and juggling, but not too bad.
I agree with Jonathan, though that it would be nice to be able to export stories/tasks by forward looking sprint, or at least the "view in issue navigator" option for all the different groupings in greenhopper (sprints, backlog, etc.)
Don't know if anyone else ended up using greenhopper this way, but it was nice to be able to edit the "fix version" in a story or task and have it show up in the appropriate sprint in greenhopper. I used that as much as I did dragging and dropping around the planning board.
Thanks for responding Shaun!
I really think making the "sprint" field more solid would be a great feature, and I can't see the downside. As it stands, using Greenhopper for longer-term planning is somewhat difficult, because anyone on the team can move things around and change the scopes of future sprints with pretty much no visibility...
Two vulnerabilities have been published for Confluence Server and Data Center recently: March 20, 2019 CVE-2019-3395 / CVE-2019-3396 April 17, 2019 CVE-2019-3398 The goal of this article is...
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