Hi, I created user stories on the a parent project level because several child projects need to work on the same story. But when I go to child project level, I don't see the upper level US so I cannot create a sub-US for the child project to work on. How can the sub-project level see the parent level US?
Thanks.
Comments
Hi Yuan,
In the project selector (project drop down in the top right) check the box "Also show items from:" for Parent projects. This will show stories for parent projects.
Barry
Reply to this Comment
Be the first to rate this
|
Sign in to rate this
I tried this out. The product backlog is now visible in the child projects, but the release backlog is not. How do I make the release backlog visible in the child projects? My intention is that the release created for the parent project is the same release for the child projects.
Reply to this Comment
Be the first to rate this
|
Sign in to rate this
Hi Eric:
If you create the release from the parent project and click the "bulk create" checkbox (top of the dialog) it will create the same release schedule in each of the child projects. Then the release backlog of the children will be visible in the parent and vice versa (if "show items from parent" is checked).
Hope this helps,
Barry.
Reply to this Comment
Be the first to rate this
|
Sign in to rate this
Thanks, Barry. I did everything that you explain. I've set up the following project structure in our sandbox.
--> Parent Project
--Sub project 1
--Sub project 2
--Sub project 3
The product backlog has been defined for the parent project. I can see the same product backlog in each sub project. however, if I assign a user story to one of the sub projects, Sub project 3, I can see this user story when focussed on the product backlog of the parent project, but not in the product backlogs for sub project 1 or sub project 2. Also, the release backlog is different for all 4 projects.
Again, I was hoping to see the exact same product backlog and release backlog for the parent project and the three sub projects.
Reply to this Comment
Be the first to rate this
|
Sign in to rate this