Our developers work from Sprint Boards, and they drag tasks into Closed stage. However, this leaves stories as New / Active when all tasks are done, and there is no easy way to know if story has all tasks completed
Is there a way to auto-close story when all tasks are done (without any additional plugins)?
Is there a way to identify what stories have all tasks closed/resolved?
Work items have independent states. Most of our experiences will not include automatic updates based on hierarchy. Either based on parent to update child or based on child to update parent.
You could refer Taylor's comment in this thread--User Story status closed but child Task still active?
Even though there is not any build-in solution, you could use some 3-rd party tool to auto change parent states: TFS Aggregator .
Another sample using Webhook to handle this. Detail solution here: https://twitter.com/danhellem/status/1173614918333030400?s=20
which leads to: https://github.com/microsoft/azure-boards-automate-state-transitions
Related
There are many presentations that talk about being able to synchronize work between the management and the implementation level in Visual Studio Team Services. That is, a manager can create a set of Epics of Features and the children of those (User Stories or Work Items) will reflect the goals of the project.
However, I could not find a way to re-order parent work items (Features) so that this re-ordering of their Backlog Priority gets updated in the backlog/board that contains children work items (User Stories).
So, my question is: Is it possible to re-order Epics/Features in VSTS and get their children (User Stories) get automatically re-ordered as well?
The only progress that I have done is turning on "Show parents" in the User Story backlog and being able to re-order parent Features in the User Stories backlog. This does not affect the order of the User Stories in their backlog or on the Kanban board.
No, it's not supported.
The priority or stack rank reorder only affects on the the Backlog/board of the specific work item type itself. That means you need to separately set the order of Epics/ Features/Stories.
So, if you want to do actions against the child work items based on their Parent order, then as a workaround just as you mentioned, you could "Show parents" in the Parent backlog and Expand the level (click the Plug + icon) to show them. See below screenshot for example.
However the requirement sounds make sense, actually there is a similar User Voice submitted here to suggest the feature, you can go and vote it up to achieve that in future, VSTS team is listening your voice.
Is there a FREE way in JIRA to require that a parent issue can't be
advanced to a state until the children (sub-tasks) are advanced to an
equal or greater state?
FOR EXAMPLE: Suppose an issue has 4 sub-tasks: 3 in PROD state and 1 sub-task is in UAT state. I shouldn't be able to advance the main issue to PROD until that 1 sub-task is advanced to PROD first so all my sub-tasks are in PROD state. Same thing with CLOSING an issue when sub-tasks are OPEN.
There is no such specific post function out of the box from Jira but you can surely write your own plugin or Groovy script(this needs script runner plugin) which can do this job.
Simple condition like, you cannot close parent issue unless sub tasks are closed can be achieved as simple as this: https://confluence.atlassian.com/jirakb/preventing-issues-from-being-closed-while-their-sub-task-are-still-open-724928276.html
Other helpful discussions can be referred here:
https://answers.atlassian.com/questions/142131/parent-issue-needs-to-close-once-sub-task-are-closed
https://answers.atlassian.com/questions/262497/close-subtask-when-parent-is-closed
https://jamieechlin.atlassian.net/wiki/display/GRV/Post+Functions#PostFunctions-Autocloseallsubtasks
Thank you,
Yes, under the transition Conditions. Add a condition Called "Sub-Task Blocking Condition.
Then, select the statuses the sub-task requires before the parent tasks can move forward. You can select more than one, so select the statuses that are equal to or greater state. Heads up though: the selection page shows all existing statuses, not just the statuses used for that workflow.
Do this for each step you want restricted.
I have a portfolio set up for my Project in Jira. It contains 6 or 8 epics and there are varying numbers of Jira tasks associated to each epic.
The Portoflio Scope view shows the epics and the tasks under each epic but the progress bar displayed for each epic or it's linked tasks does not show progress, even for epics where 90% of the tasks are marked resolved or closed.
All tasks have Original Estimates, Remaining time and those that are resolved, fixed have time logged against them.
I cannot find anything useful int the Jira Docs for tracking progress. I presume this is down to some smal config option or some feature of the epics or tasks but I cannot for the life of me work out what it might be.
We are using the cloud version of Jira.
Any ideas?
OK, so we found the reason behind my issue. By default the portfolio Scope view was showing epics for my project with the 2 releases I was interested in. There is a More option on this filter and under that was Completion date.
By default this completion date seems to be since the beginning of: Current Sprint. This meant that all tasks marked resolved or closed were excluded from the list of tasks under the epic on the portfolio board...hence, no progress.
I'm not sure why tasks listed as completed under the current, active sprint were not listed based on the default Completed filter though? Maybe it is because the portfolio was set up based on a Project rather than a Sprint Board?
Anyway, changing the completion date to something else then meant the completed tasks were included under the epics and I am now seeing lots of green progress bars!
I am trying to understand how to operate Team Foundation Service with scrum methodology. A problem of mine is:
I have a Product Backlog Item and five Work Items. Three Work Items are assigned to the backlog item and are displayed on the "board", so I can move them in between to do, in progress and done. Two other ones are not being displayed on board. Why? How can I assign them to the backlog to be able to see them on board?
This is not supported by the board, unfortunately. For the tasks to show up on the board, they must be a child of either a PBI or a Bug (or any work item that is in the Requirements category).
I was able to accomplish this by creating a new task, then link the backlog item to the task using the ID# as a Parent item (it also works by adding as a Child item as stated by #JamesTupper). After saving, the item showed up on my board. Hope this helps!
I have accomplished this by creating a "Project Tasks" spike to get these types of tasks to show up on the board in their own lane. You can also estimate this SPIKE, if you want to make sure this work is counted in your velocity, but I tend to treat these as "overhead" tasks that don't deliver value, so I don't report on them in our velocity.
If the tasks are related directly to the value you are delivering (for example, you are performing an investigation spike to determine how to estimate a user story) you should definitely estimate that PBI, give it points, and then add those tasks to that PBI.
Either way, adding the tasks as children of a PBI is the way to get them on the board.
If I understand your question correctly, search for the work items that you want to assign to a backlog item. Right click on the task task and then choose 'Link to an Existing Work Item'. Choose parent for the link type and make sure that you know the work item ID of the back log item and enter that in the work item ID. Press ok and then save the task item in the lower part of the web page.
That worked for me.
We have the following scenario that we'd like to solve.
We create a new sprint, call it sprint "A" with a bunch of issues.
Then, we get a call from a customer which results in an emergency patch needing to be released.
Here, we'd like to create a new sprint for the patch, and move it to the top of the planning board. We're unable to do this.
I tried to create a second planning board in an attempt to solve this, but it seems like we cannot have two sprints going at once.
How should we handle this scenario of wanting to create a "patch" release cycle?
EDIT - Another thing I could do is run simultaneous sprints, but I don't know how to do it, and the post I found was not helpful at all.
Why not just add the new issue for the emergency patch to the existing sprint and rank it to the top so it will be done first? You could even configure an 'Emergency' swimlane to appear at the top of the board which guarantees that emergency issues would be shown with the highest priority.
If you really want to create a separate sprint for the Emergency fix you should enable Parallel Sprints (there's some information on this in the release notes, please ensure you're running GreenHopper 6.0.3 or above). Once you do this you'll be able to start another sprint on the same board as your existing running sprint.
Thanks,
Shaun