On 25 August 2015 at 22:32, Silvio Cretti <silvio.cretti at create-net.org> wrote: > 1) OPS-300: if I recall well, it has been already moved from 4.4.1 to > 4.4.2. Now we have to move again this to 4.4.3. Is there a reason for this? > OPS-300 was scheduled for 4.4.1 and moved from 4.4.1 to 4.4.2 waiting IDM integration to be ready (as stated in 2015-07-27 closing meeting). Unfortunately in August we didn't have the neither the guys nor the time to implement it. I have foreseen this but for what I know JIRA automatically moves open/in progress stories to the next sprint. I don't know if there is a way to reschedule an in-progress story skipping a sprint (even because I think this will generate an error in the backlog since the story will be in an inconsistent state). Regards, Sergio Vavassori -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-ops-dev/attachments/20150826/5e45eff5/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy