[jbosstools-dev] jira sprint open/closing
Max Rydahl Andersen
manderse at redhat.com
Mon May 9 02:44:53 EDT 2016
Hey,
I can't see the history of sprint-edits in jira so posting this to wider
list for info.
Someone started devex #114 on May 4th (correct date) but did not close
devex #113 so all the issues on it is still lingering in #113.
I'm sure this was done with good intentions and whoever did it might be
missing some permissions (dumb jira), but this gives everyone some extra
bookkeeping to do since when I marked #113 closed (end day May 3rd) we
ended up with:
devex #113 April 2016
74 issues were Done.
13 incomplete issues will be returned to the top of the backlog.
1 partially complete issue will be returned to the top of the backlog.
Those 14 issues I assume was on #113 for a reason - they are now no
longer on the sprint boards.
Thus two things:
A) Don't start a new sprint before the one before it is closed.
B) Please go and check the top issues in backlog to see if they are
supposed to be outside
#114
C) Please raise on mailing list(s) when/if sprints can't be closed
properly - especially
when we are in starting phase of figuring out the right permissions
needed etc. to
close/handle the sprints best in jira. I'll then be able to help
figure out what is
missing.
Thanks,
/max
http://about.me/maxandersen
More information about the jbosstools-dev
mailing list