Not able to find the release from child project when use Bulk Edit.

Document ID : KB000097308
Last Modified Date : 25/05/2018
Show Technical Document Details
Issue:

Background:
Parent project does not have the Release/Iteration as the Child project. For example, the Parent project "Group: Network Switch - Demo", the Child projects are "Team: Network Switch Fiber - Demo"; "Team: Network Switch RJ45 - Demo".​

User-added image
The Releases (2018.May) are just created for the Child projects: "Team: Network Switch Fiber - Demo"; "Team: Network Switch RJ45 - Demo".​

User-added image

And the Portfolio item F13 belongs to the Parent project "Group: Network Switch - Demo".
User-added image
All User stories under "F13" belong to Child project "Team: Network Switch Fiber - Demo" or "Team: Network Switch RJ45 - Demo".

Issue:

  1. Navigate to the parent project “Group: Network Switch - Demo” and then Go to Portfolio > Portfolio Items page. 
  2. Locate the Feature F13, and Bulk edit the User stories under F13. 
  3. Click the gear in front of the items to bulk edit the user stories below the Feature "F13".
  4. Then select “Release” filed and try to associate all items to “2018.May”

Notice that "2018.May" is not in the drop-down list.
User-added image

But you can see the release when you just edit one item.
User-added image

Cause:
Bulk edit is using the global scope to locate the releases, so when scoped to the parent, the release won't be located.   The editors use the scope of the item as it is edited.   The user can change their global scope to the project for the stories to do the bulk edit.
Resolution:
The user has to select the Child project to plan the stories, so that the bulk edit could show the correct release. And in order to see the Feature which belongs to Parent project, User should select the "Parent Projects" option from project picker. Then the user could see the PI from parent project and also could plan all stories under this PI.
User-added image
User-added image