I am a standlone dev and create my iterations in AzureDevOps. Every 2-3 weeks I create new iteration. Dashboard was updating accordingly - all the elements on it are querying the current iteration. One day when the new iteration needed to start it continued to show the old one. After several days I created a new iteration setting the timeframe from the current day at the time, append some features and tasks to it but this didn't update the dashboard. Till today it stays with the old stuck iteration.
When I check the queries al lof them behave the same way:
- I choose explicitely the name of the iteration - the query returns the results
- I choose the iteration as "#CurrentIteration" and the respective team and no results are shown.
It behaves like the current iteration is not from the selected team. But the iteration is really from the list of iterations for the team.
Any advice and help is greatly appreciated!
I found my mistake.
I was creating only the iteration through Project Settings ->Boards -> Project Configuration but was not assigning it to the team through Project Settings -> Boards-> Team Configuration.
Now everything works fine again.
I faced the same issue. All I did was:
logged out
cleared all cache
logged back in
It worked for me
Related
I am trying to come up with n Azure Board query to return the work I have performed during current sprint - which I am vaguely defining as:
Work In Current Sprint = [A] + [B]
where
A = work items where I completed development stage (or was decided at some point work is irrelevant) and
B = work items I created in current sprint, not necessarily assign to me nor my team (I spent time investigating an issue, and ended up, for instance, finding a bug, so I want this included in this "report").
The closest I could get is the query blow. Problem is it is still not quite accurate, since with regards to items I created during this sprint - I could not find a way to filter created items in this sprint only - results are showing up work items that CURRENTLY BELONG to current sprint, but not necessarily created in current sprint. The only way I see I can achieve what I want is using CreatedBy - but this only provides a "hardcoded" date range offset, at any given time. If I use an offset of 14 days backwards, running query at the last day of the sprint (considering a 2 week sprint duration) should work, but running the query at any day before that, during the sprint, will return stuff created in previous sprints.
I want this query to help me track "work I have performed during current sprint" (as defined above) at any given day within the sprint.
Any better ideas ?
You could use custom date in 'create date' to limit the work item.
And I notice you use 'work items and direct links', then you need set filters for 'Filters for linked work items' part(as you needed, like iteration path etc.). Otherwise it may return linked work item that belong to other iterations, according to the filled filter, like something belows:
I hope it could help.
Our teams are using Azure DevOps. We're using the Agile framework and an enterprise release management approach (essentially, SAFe). Our increments are based on the quarters of the year -- for us, this equals 6 sprints.
My goal is to be able to view work scheduled within the current increment as the sprints move along.
I currently have a query that displays current sprint plus the future 5, to give me 3 month's worth of work (see below).
The trouble with this is it has to be edited after each sprint so it only displays the current increment's work. (I have to change it to include the previous sprint and reduce the number of future sprints otherwise it doesn't display completed work in this increment, as well as showing upcoming work from the next increment.)
Increment Planning Query
Sorry for any inconvenience.
I am afraid there is no such increment planning query, that because the value of CurrentIteration will be different due to the change of the current date.
If you want use the #CurrentIteration macros, you have to modify this query after each sprint.
As workaround, you could specify the each Iteration value in the query, like:
With this workaround, we do not need modify the query after each sprint, just need update it after each quarter.
If above workaround not work for you, you could add your request for this feature on our UserVoice site (https://developercommunity.visualstudio.com/content/idea/post.html?space=21 ), which is our main forum for product suggestions. Thank you for helping us build a better Azure DevOps:
Hope this helps.
I have two teams assigned to one project.
Currently, they're working using the same iterations.
Starting from new iteration I want to change this setting. One team (A) will work using iterations 2 weeks long, the other (B) 3 weeks long.
I am looking for answers to the following questions:
will team B board be cleared (I'm fine with that, just want to be 'ready' for that)?
will team A board be affected by the change of team B settings?
If I'm understanding your scenario & questions correctly, going into the new sprint (iteration) you would like to split your team's iteration duration. Team A to 2 week iterations and Team B to 3 week long iterations.
If that's correct, then changing your team's iteration duration shouldn't have an affect on the boards, meaning backlog and sprint boards. You may want to look at adjusting your team member's capacity. Also make sure when you create new iterations to add them to your team configurations, and look at what your teams' default iteration is.
For this issue , creating a new iteration for the team will not clear the previous team board.
And the change of team B will not affect team A.
You can switch iterations of different periods of the team in Spirits.
I'm looking to create a query that shows all of the stories that were added to the sprint during our sprint planning meeting. This meeting always takes place on day 1 of the sprint.
Naturally, some stories may be removed mid-sprint but I'd still like to see what was originally planned.
Equally, some stories may be added mid-sprint and I wouldn't want to include those.
I noticed that the built-in Velocity widget has a 'planned' bar, but I'm not entirely sure how that's calculated.
For this issue ,deleted work items cannot be displayed with other work items in queries. If you want to query the stories created by a certain period of time, you can do it in two steps.
First you can query the stories created in the initial time period by the following conditions.
Then you can add the Created Date and Iteration Path column in Recycle Bin to find the stories deleted in this time period.
If your stories are permanently deleted(Remove from Recycle Bin), then you will really cannot query them.
I´ve DELETED a Sprint by mistake and their related work items I went to the reclycle bin but I can't find those over there or the referred sprint. Has some one a solution or suggestion for me?
<TL;DR>
Work items aren't removed or deleted when deleting a sprint/iteration.
The Iteration field in Azure DevOps holds the Sprint value. When you delete an iteration, the Azure DevOps will ask what new iteration to assign the work items to. I think, by default, it assigns to the Team's Default Iteration:
The work items are still there, recreate the iteration if you want and move the items back into it.
If this isn't what you did, you may have removed the sprint from the Team's list of selected sprints.
If this is what happened, simply choose the + Select Iteration(s) button to add it again: