Is it possible to get the user stories (Hierarchical Requirements) from a specific day in an iteration using the Rally Web Service API? I'm developing a java application which will generate a history chart for an iteration. For example if the iteration was 14 days long, I need to get the Hierarchical Requirements with all their attributes for each day in that iteration, something like: [day1,Hierarchical Requirements], [day2,Hierarchical Requirements], and so on.
Check out the IterationCumulativeFlowData object in the WSAPI.
https://rally1.rallydev.com/slm/doc/webservice/
That should give you the total number of items and their todo/estimate totals for each day.
Related
I am attempting to retrieve all work items currently or previously associated with a given Iteration from Azure DevOps, either through an in-system query or through the API. I need this information to calculate sprint predictability metrics.
As far as I can tell, ADO only stores the latest Iteration in the work items fields, so the API call to ask for tickets associated with a Past iteration does not include any tickets that may have been moved to a different iteration mid-sprint. Likewise, they query options do not allow for something like a "was" operator to test for work items with may have met the criteria in the past.
Short of pulling each work item history individually through the API and creating my own iteration timeline for all tickets in the system, how can I get this information?
Take a look at this. You have to use the "was ever" operator in the iteration path. To do so, you have to query for it using the WIQL-Syntax.
So you'll have to add
...
AND (
EVER (
[System.IterationPath] = #currentIteration('[YourTeam]\... <id:...>'))
to the WHERE part of the query.
If you want to see an extended example, look here
I am trying to create something similar to what the weather apps have which show a graph of the temperatures from today.
I am currently using the onecall endpoint which returns the current weather along with forecasts for the next 48 hours but this doesn't cover my case of showing earlier data from the day.
Am I miss using this endpoint or is there a way to show the data for the current day (both historical from earlier and forecast for later)? Or do I need to use the historical data endpoints?
Is there a way to get search counting, similar like sql: select count(*) where name='xxx' in Usergrid 2.1.0-rc1?
I developed a cash app. Users download offers in my app and I reward them their downloading. I will need to know how many offers user download every day, every week and every month to manage their level. So I am expecting a feature to let query the counting instead of always return the entities.
What is your recommendation way to do that in Usergrid 2.1.0-rc1?
As far as I know, count isn't supported in queries. You could increment a counter every time the user downloads an offer, then do a time interval get on the counter
http://usergrid.apache.org/docs/counters-and-events/retrieving-counters.html
For Active Collab team watching this tag.
I am working on a project that uses new Active Collab 5 API, I am having performance issue trying to run reports.
Example I try to build reports on date-range, and currently to achieve that I need to first run a call to get all projects.
Followed by a loop with this call:
API::get('/projects/'.$id.'/time-records/filtered-by-date?' . http_build_query(['from' => $from, 'to' => $to]))
However we have a large number of projects, in addition to high number of active projects we also need to filter Archived projects as well to get correct reports for billing.
Now I work with around 1500 projects in AC.
So I need to make 1500 API calls which takes a huge performance hit. Is there a way that you can possibly build something that would work along these lines.
API::get(/timerecords/filter-by-date);
with a possible passed parameter that will say (all, active, complited) project state.
Please let me know what you can do or if I have missed something in your documentation that already does this.
Thanks
What you need here is not a request that goes through all projects one by one, but a request that it tailored for cross-project reporting. Active Collab 5 has just the right API endpoint for that - /reports/run.
As an example, you can use this command to query time records and expenses from all active projects that were tracked today:
curl -H "X-Angie-AuthApiToken: YOUR-API-TOKEN" "http://your.activecollab.com/api/v1/reports/run?type=TrackingFilter&project_filter=active&tracked_on_filter=today"
Notice the route (/reports/run) and query arguments:
type - specify type of the report, in this case time and expense tracking report,
project_filter - specify project filter. Apart from active, other useful values of this filter are completed (for completed projects), selected_1,2,3,4 (selected projects with a list of project ID-s), client_1,2,3,4 (projects for clients with the given ID-s), category_1,2,3,4 (projects in categories with the given ID-s),
tracked_on_filter - filter by the date when records were tracked. To target a particular date use selected_date_YYYY-MM-DD and to target a date range use selected_range_YYYY-MM-DD:YYYY-MM-DD.
tracked_by_filter - filter by who tracked the time. It can have various values, like anybody, logged_user, selected_1,2,3.
To list only time records, set type_filter to time (or to expenses if you want only expenses to be listed).
I am trying to do some analysis on team member contribution in Rally. The quantitative data will supplement the qualitative data about how much value a team member creates. Our teams work on user stories with story point estimates and each story has 1 or more tasks with hour estimates.
I'd like to take the hour estimates to determine what percentage of the user stories that each team member contributed and then total the fractions of story points for each developer each month.
Has anyone else solved this?
You may start with a code example here that builds a grid of stories and associated tasks that displays ScheduleState, PlanEstimate, TaskEstimateTotal, TaskRemainingTotal, Owner values for stories as well as State, Estimate, ToDo, and Owner values for associated tasks. The stories are filtered by iteration.
The grid is based on Rally.data.custom.Store, which allows adding custom columns (that do not correspond to actual fields in Rally object model). Those columns can be populated by values derived from whatever calculation logic you code in your app. There is no built-in mechanism of deriving individual contributions in Rally.