Using GreenHopper Scrum, I have dragged several issues to Sprint 1
I'd expect 2 things to happen :
a) using JQL to be able to search for issues with gh.sprint.customfield.default.name = ' Sprint 1'
b) on the issue view/edit screen, provided that the field gh.sprint.customfield.default.name is enabled for it to show the sprint name.
No such luck. for both a) and b) this field gets populated only when we start the sprint.
Is that by design ? Where's it actually storing the sprint mapping before I start the sprint ?
IF it's by design, this is really cumbersome and makes Sprint Planning much less valuable and integrated with JIRA; I actually want to produce reports with the field gh.sprint.customfield.default.name even for sprints which are planned and not due to start for months to be able to tell people when itereations are planned and who is doing what months from now.
2) Even if I do start the sprint, the gh.sprint.customfield.default.name is populated with a internal numeric id on the edit screen. (on the view screen I'm getting the correct Sprint Name)
Sometimes if I am editing an issue, assigning it and transitioning it through the workflow, it would be great to be able to also see the Sprint Name and chose another sprint if needed, (i can do this now, but I need to remember the numeric id of each sprint. )
Your help is much appreciated. I'm getting the feeling that issue a is by design... can anyone confirm this?
Solved! Go to Solution.
Thanks for the info:
Looking forward to the next version.
Any idea when 6.3 is coming out ?
No official date yet, but it shouldn't be too far away :)
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Apply agile practices
Transform how you manage your work with agile practices, including kanban and scrum frameworks.
Learning Path
Configure agile boards for Jira projects
Learn how to create and configure agile Jira boards so you can plan, prioritize, and estimate upcoming work.
Jira Essentials with Agile Mindset
Suitable for beginners, this live instructor-led full-day course will set up your whole team to understand how to use Jira with an agile methodology.