I am a new user of Rally and would like to know if there is a way to create sub-tasks in Rally. I am able to create tasks from within a user story, but not from within another task so it doesn't seem possible at first glance.
In Rally there are no subtasks, and tasks cannot have child tasks.
Related
I am a DBA and I work across all of our dev teams. I often will get a task on someone else's user story. I will not be a member of the team that the user story belongs to. I need a way to see all of the user stories that I have a task on so that I can easily track the status, etc of the overall user story.
We are using Rally/Agile-Central
The best way is to use the Custom List app and go to a location in the project hierarchy above anywhere you might have a story or task assigned to you. If you then ask it to filter on owner equals you, then it will give you the stories you own, but also the stories owned by someone else that you have a task assigned to you.
It does the equivalent of this query for you automatically:
((Owner = daniel#acme.com) or (Tasks.Owner = daniel#acme.com))
I am using this rally API to get the list of all the stories:
https://rally-n.rallydev.com/slm/webservice/v2.0/hierarchicalrequirement?query=(Project.Name="My_Parent_Project")&order=OrderString
My_Parent_Project actually do not have any user stories, but its children projects (my_child_1 and my_child_2) has user stories.
Is there any specific field, which I can mention to get all the user stories including child projects.
I can see Rally UI has option to get the data from Child project. So I believe there must be an option to get this data using above API. (They use projectScopeUp=false&setScopedDown=true which doesn't seems to be working with
"hierarchicalrequirement" API.
You're really close.
It seems like you've already found the project scoping docs:
https://rally1.rallydev.com/slm/doc/webservice/projectscope.jsp
I think if you just swap your (Project.Name = "My_Parent_Project") query to instead use the project=/project/12345 query string parameter and include projectScopeDown=true you should be all set.
In TFS 2015 using the Agile process template, the board for the "Stories" backlog shows only stories, and the board for the current iteration shows all tasks under stories. This makes sense for most teams.
We are breaking down our work into smaller than usual stories and thus avoiding task breakdown, so very few of our stories have tasks. Is there a way to show stories on the current iteration board instead of tasks, so that it looks similar to the higher-level stories board but with only the stories in the iteration?
In the end, I want to avoid a useless board like this:
Have you considered just using the Kanban/Backlog board?
My team don't use tasks at all, all our work is tracked on the Kanban board, we never use the Sprint Board.
Some teams add a "Sprint Backlog" column to show what is planned for the current sprint. Then you can collapse the "New" column until the next planning session.
I am making a calender app where someone could edit a task.
I have a task which has got task name, description and due_date. This task has to be repeated on a quarterly basis. If someone goes to the task of the next quarter and clicks on the task, I want an object to be created at that point of time with due_date of this task so that other operations like editing can be done on it.
I am able to show the tasks on calendar but don't know how to start with saving the object thing.
Since I am using ice_cube to make recurring event I thought I could do it with persistence as per the wiki. However I seem to be stuck and don't know how to move forward.
It will be great if someone can point me on how to make this use case
The solution which is working for me is following :-
1) Identify that the event is recurring and not the one which is saved in the database (IceCube will help in this)
2) When click on the event which is recurring pass a parameter with the link (say recurring event)
3) Check in the controller if the parameter is recurring event then create a task in the backend and redirect to the show of that task (while creating the task fill the details of the task in the backend)
Hope this helps
i'm writing a simple application to build a task dependency tree (i declare a dependency by commenting on a task "Depend on: ") using asana API, it is indeed a simple task and should also be a simple and quick script, but i got to a bottle neck here.
From the API documentation i get that i need to:
Query the project tasks using /project//tasks
iterate trough tasks to:
get complete task information, since i'm only getting id and name.
Get task stories.
what i would like to do is a simple api call to get all this information at once, like:
/project//tasks options.expand {task, stories}. Am i missing something or this it not possible?
Complete information about tasks you can get with one request thanks to "opt_fields" option (https://asana.com/developers/documentation/getting-started/input-output-options).
Unfortunately "stories" still need another request.
No. As seen in the asana queries are tree-like structure. To get the story you require workspace_id > project_id > task_id & task_id for story. I recommend that you use a loop. Tasks of the project for getting information on the tasks and history. Upon receipt of the task id - send two requests info task & stories. Thank you, Ruslan.