I created a scrum Rapid board and assigned a filter which pulled in the issues for the Sprint. I moved the Sprint marker underneath the last issue and clicked on Start Sprint and the issues are now visible in Work Mode.
However, I did not notice the Plan Mode instruction until afterwards, they seem to suggest that you must prioritise first! I need to reorder the issues but in plan mode now it seems only the sprint name and dates can be changed. However one can reorder in work mode to reprioritise - phew.
I missed adding an issue as it was recently added and I did not refresh my rapid board before clicking start Sprint. Is there a way of way of deleteting the created Sprint so I can do it properly next time?
Currently, there is no way to 'delete' a Sprint. But, you can simply 'complete' it from the Work mode, which will return all not done issues to the backlog in Plan mode. From there, you can create another Sprint.
In version 5.9.1 of GreenHopper, you will be able to add issues to a running Sprint from the Plan mode, so you do not have to strike off the Sprint and create a new one.
I hope this answers your question.
Michael Tokar [Atlassian]
Thanks. If I complete the sprint, is there somewhere it can be viewed in a historical way? I could always first rename it to Dummy or somehting before completing.
What about the people like me who are stuck on Jira 4.4 (getting an upgrade form 4.2 took many months and was only completed recently (before 5 came out), so I am not sure when we can upgrade to Jira 5. So we are stuck with v5.8.7 of GreenHopper. Will the 5.8.x track be updated for us 4.4 people or only 5.9.x?
You can view the issues that were in a Sprint but at the moment this has to be performed using a JQL query. We intend to add a historical sprint report to one of the next couple of releases.
Unfortunately JIRA 5.0 has a number of very significant improvements that GreenHopper is reliant upon (particularly improvements in the Active Objects data storage plug in). We would recommend upgrading to JIRA 5.0 at the earliest possible opportunity. There will be no further releases of GreenHopper for JIRA 4.4.
The Rapid Board knows which Sprints exist by looking at all of the issues selected by the board's filter then looking at the Sprint field.
We generally do not recomment editing the Sprint field directly, but if you cleared the Sprint field of the issues that appear in the report that should cause the Sprint to no longer appear in the Rapid Board.
I'm using JIRA 5.2 and Greenhopper 6.1.4.
I had started a wrong Sprint.
I have deleted the Sprint from the JIRA_Sprint table
I have deleted all customfields with a link to the JIRA_sprint.
There are no more issues pointing to that Sprint.
The sprint appears in the drop down of the scrum boards (sprintboard and so on)
And it shows stories linked to the sprint in the scrum board but not in the other JIRA views.
It also appears in the drop-down for JSQL queries.
Is there a "archive" table that stores old links to sprints from issues?
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