If I drag a parent (say Feature) in Kanban board (say from Open Status to closed Status), then the status of its childs (say User stories) is not changed.
Similarly if I drag all childs (say User Stories) in Kanban board (say from Open Status to closed Status), then the status of its parent (say Feature) is not changed.
Is this the expected behavior? Please throw some light?
This is the correct phenomenon for now. You can use some third-party extension to achieve this for a workaround.
And there has been a feature request in UserVoice, you can also vote up for it:
Automatic State Transition based on linked Work Item State
https://visualstudio.uservoice.com/forums/330519-team-services/suggestions/2830827-automatic-state-transition-based-on-linked-work-it
Related
case 1
1. Create custom fields called "completion %" which depends on child user stories. How can i fill parent user story completion % based on child user stories completion
Create two custom fields - start and end date => parent user stories should NOT depend on child user stories start and end date
any idea on rally custom fields changes
It sounds like you should start using Portfolio items to be the parents. Having parent user stories and child user stories is from a time when Rally didn't have the capability it does now, and there are far better ways to manage your work breakdown.
What you are asking for is already available in Rally if you use Features as the parents of a collection of User Stories.
The custom list app is a nice app, to show a list of items that are currently in Rally.
What I would like to get out of this list as well, is UserStories and Defects from previous Iterations.
A page can be easily setup where you have an iteration filter on top, then a list app underneath. When the page is set to show closed / past iterations it should show the user stories and defects that have been previously assigned to the applied iteration (even if they have another iteration set currently).
Is such an app available? Searching a bit did provide any usefull apps,
Blocking history seems to do a little in that area, but looks only at things that had a blocker flag set:
https://github.com/RallyApps/app-catalog/blob/master/src/legacy/BlockingHistoryApp.html
The List from this app on the other hand cannot be modified, therefor I want to combine history with the Custom Grid app as provided by Rally.
Regards
What about the Iteration Scope Change app?
Source here:
https://github.com/RallyApps/app-catalog/blob/master/src/legacy/IterationScopeChangeApp.html
It's available directly in the app catalog in the product as well.
After upgrading to TFS 2015 I have a bunch of tasks showing up under Unparented in the Backlog for the current iteration. These tasks all have parents though. Going through each task it looks like the parents are all User Stories in Active or Removed states. Resolved User Stories are showing up with their Tasks just fine. How can I get Active and Resolved User Stories to show up in the backlog with their tasks?
Turns out I had to edit my process configuration and add Active, Removed and a few other states to the <States> of the <RequirementBacklog> section.
Used:
witadmin exportprocessconfig ...
to export the config, edited it in notepad the
witadmin importprocessconfig
to import the update config
See here for more
You can track unparented tasks in similar ways to other tasks, or drag
them to an existing backlog item to parent them. The Unparented card
tracks the total of remaining work defined for all unparented tasks,
however, it isn’t associated with any work item.
source: Task board from MSDN
We show the parent User Stories if they satisfy these rules:
it needs to be New, Active, Resolved or Closed. We don't show Removed User Stories
it needs to be in an area path that is used by the team.
My suspicion is that the second requirement is not true. There is also a button on the toolbar that says "Create Query" that gives you the query we use to get the data for the task board for further debugging if needed.
I’m just looking for a sanity check before I go down this road with my Windows Store App.
In the app, I am looking to have a navigation model which involves the following:
All users shown the initial page, and are asked to make a section of Items from a list before tapping continue.
Each Item has a group of pages associated with it – could be 2,3, whatever.
The user is then presented the pages in the order that they are associated with for each Item and in the order by which they selected the Items.
For example, say the user selects Items 2 & 3.
Item 2 has PageA, PageB, PageC associated with it
Item 3 has PageB, PageD, PageA associated with it.
The user journey for the App would be
Selection -> PageA -> PageB -> PageC -> PageB -> PageD -> PageA -> End
The approach I am thinking of going with involves a “UserService” which is persistent throughout the app and stores a list of the Items the user has selected (in order)
I would then have a “PagePlayer” page which would act as a container for the pages to be displayed and this would be loaded after the user is finished with the Selection.
The player would then display all the pages in order based on the Items that were saved in the UserService.
I personally don’t want to go down this road because I know that having Frames displaying Pages etc is generally a bad idea, it could ruin the navigation history etc.
Which pages are associated with each item I would have saved to a local file of some sort and have this loaded when a new Item is set to be displayed.
The number of items are “hard coded” and have IDs associated with them.
I am familiar with Prism for WPF but unfortunately the recently released Prism for Windows Runtime does not support modularity for using a composite approach.
Apologies for general-ness of this question, I couldn’t think of another way of asking it.
Any help would be greatly appreciated!
In RTC source control when I expand the Team Area I have this view :
I can see the stream and its components. What decides if components should appear in Components folder ? As can be seen in screenshot this is currently empty. For other developers this is populated with components even though they cannot see the streams ?
You see all components that are visible to you.
In other words, it depends on the ownership for each component.
Any component owned by the project area or your Team Area would be displayed in the Component section.
Any component owned by a single resource (a member of the RTC project area) or another Team Area (that you aren't part of) won't be displayed there.
The same would apply for the streams: check the owner of those streams to understand why a resource doesn't see it.
Whats the point of hiding a stream if the components themselves are not hidden ?
The point (in hiding Stream even though it doesn't hide component) is preventing users to deliver to that stream: they can still work on the same set of component (visible because of the right ownership), but they can no longer see (and deliver to) a given Stream.