Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #8517 Stories created under Sprint Milestone on V2 Planning are not linked to their Release
    Actions
    Infos
    #8517
    Patricia Carrasco (pcar)
    2015-12-01 16:39
    2015-10-19 22:33
    8648
    Details
    Stories created under Sprint Milestone on V2 Planning are not linked to their Release
    Epics are not planned on the Agile Dashboard. We plan Stories in Releases and Sprints. If a story is created from the Sprint Milestone on the V2 Planning it does not get linked to the Release artifact.
    Agile Dashboard
    8.7
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Patrick Renaud (patrick.renaud), Emilio Palmiero (empa)
    Stage
    Empty
    Closed
    2015-12-01
    Attachments
    Artifact links
    Empty
    By Patricia Carrasco (pcar)
    (16 kB)
    project_tracker_hierarchy.PNG
    Deep tracker hierarchy
    References
    Referencing request #8517

    Artifact Tracker v5

    request #8616 User story created under a planned Epic should not be part of the Top Backlog
    rel #8547 8.9

    Git commit

    tuleap/tuleap/stable

    Merge commit 'refs/changes/54/4754/12' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD 72bb469251
    User avatar Benjamin Dauton (bdauton_enalean) , 2015-12-01 16:35
    request #8517 Stories created under Sprint Milestone on V2 Planning are not linked to their Release c03486cdef
    User avatar Joris MASSON (jmasson) , 2015-12-01 16:20

    tuleap/u/mildred/tuleap/stable

    Merge commit 'refs/changes/54/4754/12' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD 72bb469251
    User avatar Benjamin Dauton (bdauton_enalean) , 2015-12-01 16:35
    request #8517 Stories created under Sprint Milestone on V2 Planning are not linked to their Release c03486cdef
    User avatar Joris MASSON (jmasson) , 2015-12-01 16:20

    Release

    release #114
    Referenced by request #8517

    Other

    gerrit #4754
    Display settings

    Follow-ups

    User avatar
    Benjamin Dauton (bdauton_enalean)2015-11-23 11:47
    Hi all,

    Concerning the deeper hierarchy question, we think that there will not be performances issue. What we will implement is: when an item is created in a milestone (e.g. a User Story in a Sprint), we will check if its parent is already linked to the parent milestone (e.g.g Epic in Release). If no or if the item has no parent, the item will be linked to the parent milestone (e.g. User Story will be linked to Release). If yes, nothing will be done.

    Concerning your issue @patrick.renaud, I've reproduced the problem and I confirm there is a bug in the top level backlog. It shouldn't list user stories linked to planned epics, in other words, it shouldn't list items which are indirectly planned (indirectly = planned because their parent are planned). I open another request because it's a different issue.
    User avatar
    Patrick Renaud (patrick.renaud)2015-11-19 18:03
    Benjamin,

    Sorry, to answer your question: Release Planning allows the planning of both Epics and Stories in a release. The same goes for Sprint Planning. I never actually schedule an epic into a sprint; it's just that if I don't include epics in the sprint planning definition then I don't get to see the epics at all in the release backlog of the sprint planning view.
    User avatar
    Benjamin Dauton (bdauton_enalean)2015-11-19 16:27

    Hi all,

    Any news concerning my two questions?

    1. If you have a deeper tracker hierarchy (Release > Sub-release > Sprint), do you want that the User Story to be linked to the Sub-release AND the Release ?
    2. See my previous comment concerning @patrick.renaud 's question.

     

    User avatar
    Benjamin Dauton (bdauton_enalean)2015-11-10 09:12
    Hi,

    I also agree with you @pcar and @patrick.renaud, user should not have to click on the "inconsistent items" button, which means nothing to the user. I just wanted to confirm the behavior.

    Concerning the last point @patrick.renaud, what is your AgileDashboard configuration? Release planning where you can assign Epic into Release and a Sprint planning where you can assign User Story to Sprints with this tracker hierarchy: Sprint under Release and User Story under Epic?
    User avatar
    Patrick Renaud (patrick.renaud)2015-11-09 16:47
    Hi,

    Yes, I also agree with what Patricia just said.

    I would like to highlight an aspect that may have went by unnoticed in this conversation. It is important to take into consideration the context in which an action is executed by the user. I have this case that results in the creation of a story in the top level backlog even though I am located in the Sprints PlanningV2 screen. To do this, I simply select an Epic from the Release Backlog and choose +Add a User Story. Although the resulting story is linked to the Epic, as expected, it ends up unplanned, in the top level backlog, when I would have expected to see it under the curreny release backlog instead.
    User avatar
    Patricia Carrasco (pcar)2015-11-09 16:08
    Hi Benjamin, I discussed this with Emilio and we believe that the V2 should automate what clicking the "Inconsistent Items" button does as of today. Our user find that button very confusing and don't really know its purpose.
    User avatar
    Benjamin Dauton (bdauton_enalean)2015-11-09 10:13
    Hi Patricia,

    I confirm that if you create a User Story in a Sprint (submilestone of a Release milestone), this User Story will not be linked to the Release. This was already the case with the content/planning v1 views: if you create a User Story in the content view of a Sprint, this User Story will not be linked to the Release. In both cases, you'll find this User Story in the content view of the Release under the "Inconsistent items" list with a "Resolve inconsistent items" button.

    Questions are:
    - Do you want to match to the current content/planning v1 behavior?
    or
    - Do you want to automatically link the User Story to the Release and if yes, if you have a deeper tracker hierarchy (Release > Sub-release > Sprint), do you want that the User Story to be linked to the Sub-release AND the Release ?
    • Status changed from New to Verified