...
Nikodem Graczewski (Unlicensed) Paweł Gesek Note: At the Sprint Q&A meeting, we would like to hear you describe these tickets and tell us what order you might work on them in. We basically want to see if these tickets make sense. We want to start giving tickets more context/user story understanding. One of our ideas from Retrospective meeting was to ask you to describe the tickets and your proposed order during Q&A meetings as a way to see if the tickets make sense. -Brandon
Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-239 -
(Team Parrot: We have tried to make 1611 a true User Story without giving so many technical implementation details in this ticket. Please review and let us know if you choose to make sub-tasks for the technical details. If there is technical design, please give Team ILL a chance to review. Team ILL would like to hear whether this is helpful to keep tickets high-level.)Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-1611 -
Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-3726 -
Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-3818 -
Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-3805 -
Jira Legacy server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-529
...