I want to find all "orphaned" user stories in Rally, where a user story does not belong to any feature. I know I need to set filter to((PortfolioItem = null) AND (Parent = null)) but where do I do that? Where do I start?
Forgive my ignorance, I am new to Rally
You have a bunch of options: the Work Views page or a custom list app are both decent places to start. Both of those apps have filters where you should be able to select a filter for Parent = -- No Entry --
To select the orphaned user stories, the below steps while tracking every iteration status would help,
Add Filter on field 'Feature'
In the filter for 'Feature', choose the value '-- No Entry --'
This would give you the list of user stories which are not linked to a parent feature in the respective iteration
Related
enter image description here
I'm trying to find an efficient way to select all dependencies. The idea behind this table is:
Each taskID is a task that will be display to the user.
When taskid 22180 is selected by the user and completed it will
automatically enable the other tasks (activateTaskId = 22180) to
become available to the user hence inactive = 0. Up to that point
everything is fine.
What i need help at is when you have subsequent tasks.
So when taskid (22180) is selected and completed by the user the following tasks become available (22181,22182,22185 and 22186). As you can see if the user selects 22182 then the task dependent on it is 22183 and subsequently 22184 will .
how would i efficiently select all the task that branch off the initial one (22182) no matter how many may exist ?
Thank you
I'm trying to create a view in CRM 2011 that will show a few columns from Customers (Account), Orders (SalesOrder), and Order Products (SalesOrderDetail). I already know I need to start at the child-most entity so under Advanced Find I select "Order Products" under Look for. When I do this I'm able to select columns from Orders but unable to select columns from Customers.
Is this even possible to accomplish in CRM?
I'm trying to create the following result set:
Account.Name,
Account.Email,
SalesOrder.OrderNumber,
SalesOrderDetail.NetAmount,
SalesOrderDetail.ShipDate
I verified that you cannot manually add a second link within a view query. To my knowledge it is also not possible to add these columns though javascript. You can get the account name in your view simply by using the account lookup on the Order. If you need for the account email to also be in the view, then I suggest you add this field to the order entity and populate it with post callout logic on the account.
I Second Zach’s idea, but suggest adding a direct relationship between customer and orderdetail . This way you can use fetchxml to show account.email or any other account.* for that matter.
The downside is you’ll need to sync order.customer changes to orderdetail.customer.
The better option is to simply create a report and show that in an iframe or a webresource.
This is not possible even if we edit the fetch xml it wont work
Looking to create a custom app that shows all stories assigned to an iteration including that stories tasks, tests and defects but also grouped by Parent or Epic like the following and each item links to that work product item. What is the best approach to group stories by parent?
Parent Story 1
- Story 1
- Test
- Task
- Defect
- Story 2
First you will need to query to get the stories for the iteration. If you want to allow your app's user to select the Iteration you can use the Iteration Dropdown. If you query stories using the getQueryFromSelected method on the dropdown you should have the stories that are attached to the chosen Iteration.
When fetching the stories using RallyDataSource specify Tasks, Defects and TestCases as a part of your fetch string.
If you need any other fields populated fill them in the fetch string and the dependent objects will have them filled as well.
For example if you need their FormattedID, specifying that in your fetch string will also populate that field on the Tasks.
Once you have your data you just need to figure out how you want to display it.
I'm using the MSF Agile 5.0 project template.
I'm looking to modify the Product Backlog query to include tasks that have no parents. The query currently only shows User Stories.
I don't see a field to query against such as parent item id or similar.
Has anyone done this?
Why are you looking to include tasks? The product backlog is to prioritize the User stories. If you want to plan on tasks, then use the Iteration backlog.
To achieve this result you can use the "Work items and direct links" type of query. Then in the 'top grid' specify the work item type = "task" and in the 'bottom grid' specify the work item type = 'user story. Then change the linking filter to "only return items that do not have the specified links"
I'm currently logging all actions of users and want to display their actions for the people following them to see - kind of like Facebook does it for friends.
I'm logging all these actions in a table with the following structure:
id - PK
userid - id of the user whose action gets logged
actiondate - when the action happened
actiontypeid - id of the type of action (actiontypes stored in a different table - i.e. following other users, writing on people's profiles, creating new content, commenting on existing content, etc.)
objectid - id of the object they just created (i.e. comment id)
onobjectid - id of the object they did the action to (i.e. id of the content that they commented on)
Now the problem is there are several types of actions that get logged (actiontypeid).
What would be the best way of retrieving the data to display to the user?
The easiest way out would be gabbing the people the user follows dataset and then just go from there and grab all other info from the other tables (i.e. the names of the users the people you're following just started following, names of the user profiles they wrote on, etc.). This however would create a a huge amount of small queries and trips to the database in a while loop. Not a good idea.
I could use joins to retrieve everything in one massive data set, but how would I know where to grab the data from in just one query? - there's different types of actions that require me to look into several different tables to retrieve data, based on the actiontypeid...
i.e. To get User X is now following User Y I'd have to get my data (User Y's username) from the followers table, whereas User X commented on content Y would need me to look in the content table to get the content's title and URL.
Any tips are welcome, thanks!
Consider creating several views for different actiontypeids. Union them to have one full history.