Is it possible to create a custom rule or some other method to automatically move a work item from the DONE state/column to an Area called "Archive" and change the iteration to one of our archive iterations based on a rule? Ultimately we want an automated process to archive work items in the DONE column after a specific date. For example, I set up an Archive area and various archive iterations based on the quarter of the fiscal year. We have a requirement to maintain this documentation for x years and don't want to see it all in the DONE column for years to come.
Related
I would like to display the results of a query that identifies the bugs created in the current iteration. AKA "new bugs". I know this can be done by using the created date but that requires the date to manually updated for each new iteration.
Is it possible to leverage the 'current iteration' in the query? Or some way that does require a manual update.
I have tried using only 'current iteration' but this returns all bugs in the current iteration limited by the state that I specify. The result is not limited by when it was created.
I have tried to add a clause for created date, which works, but is not dynamic. meaning it does not increase as the iteration grows in number of days.
Yes, you can add a and/or clause like below
I have a second drop-down list as we have different Teams, so it wants me to tell it which Team I want to bring back items for, from the #CurrentIteration.
We've come across a number of issues with our Azure DevOps projects and are trying to surface relevant information to the management team with queries and dashboards on projects. Mainly it's just been counting the number of results for particular queries, e.g. when a status hasn't changed in 30 days, number of blocked items, total items in current sprint etc.
What we've been asked for though is to be able to rollup the original estimate total for all work items, and also roll up the completed work as another value. The queries and other things I've seen only seem to be able to count, rather than sum up, but some of the widgets I've seen do appear to sum things for graphs (but I'm just looking for the values).
Can anyone suggest anything?
I imagine that you have two different options here. The first being is that you could leverage the new roll-up columns and aggregate some of this information on the backlog view. Some of this makes assumptions about how you are grouping and the hierarchy of your work items.
Add a rollup column
In the Column options dialog, choose Add a rollup column, select From quick list, and then choose from one of the options listed.
Choose from the menu provided.
Progress bar displays progress bars based on the percentage of associated descendant work items which have been completed or closed.
Total number displays the sum of descendant items or the associated fields of descendant items. Totals provide a measure of the
size of a Feature or Epic based on the number of its child items. For
example, Count of Tasks shows the sum of all tasks that are linked
to parent items. The active or closed state is ignored. Rollup column
menu
Remaining Work of Tasks shows the sum of Remaining Work of tasks that are linked to the parent item.
If you wanted to instead see the summarized details on a dashboard, I'd recommend downloading the Query Tile PRO marketplace extension. Let's say you had a query already defined:
The options support sums based on query fields:
And so you have the tile with the summation value you are wanting. Just replace with other fields that you might need.
I was looking on VSTS, but I didn't found how to estimate our Tasks/users story in hours instead of Story point.
Is this possible?
I know the pro(and cons) of story points, buf for now our team want to move progressively with agile, and we don't want to start to estimate in story points.
Thank you!
Edit as requested, I currently use the agile template(but open to change)
Declare "One story point is equal to one hour" and use the existing field as-is.
TL;DR
Use the built-in scrum template
If you use the built-in Scrum template Tasks have Remaining Work and PBI's have Effort. Nothing says Remaing Work = hours or Effort = story points.
If you want to estimate your tasks in number of 4 hour work blocks it will take to complete you can do that, if you want to do it in hours you can do that. Same goes for effort you can put any number in there you want as long as you make sure everyone in your team understands what 1 or 5 or 10 means.
So if possible switch to the scrum template, your question is exactly the reason why these fields have a more generic name than Story Points or Remaining Hours in the scrum template. Added bonus is that your team can switch definition if they feel like some other number or unit suits your estimation process better.
This blog post makes a good comparison between the built-in different templates:
https://nkdagility.com/choosing-a-process-template-for-your-team-project/
If you are an administrator in VSTS select the VSTS button at the top left of the screen. Then select then select the cog.
This will take you to a page where you can edit a number of settings. Select Process.
In the process window choose the process your project uses. You can see which one your project is using by the numbers on the right hand side of the process. Once you’ve found your process select it by clicking.
Then choose the work item type you wish to change. So in this instance user story.
Once in the task you want to change select add group and name the group want to add and select it's placement on the card.
When the group has been added select it and choose the ellipses (...). Then select Add Field. Customise the field to be either a new one of your choosing or choose a predefined one.
Once you have added this step repeat the process on this page to customise and style the task how you like. Once done navigate back to your project in VSTS and the changes will be applied
The Cumulative Flow Diagram is useful, but its granularity is set quite large, i.e. you can only see numbers for the dates it chooses, which can be a week or more apart. However, it shows that under the hood, VSTS is recording the state of the backlog at every date.
It seems that the data must exist to find out the data I need (in this case the sum of effort for each state for PBIs) as it was at a given date - not just the dates picked by the chart for its points.
I've searched around but can't find it anywhere. Does anyone know how to do it?
To set date for Cumulative Flow Diagrams (CFD), you just need to click on the CFD and edit the date.
Such as to set the date of the CFD in backlog:
Click the diagram -> Edit -> specify the start date in Cumulative flow Tab -> Save.
Then the CFD will be changed based on the specified period.
To filter CFD by tag, type, Assign To etc, VSTS has not support this feature for now. But you can create an user voice for it, or you can calculate with your own code.
Hi good day I have a line item that will run for a year but will only have a monthly impression of 50 thousand. How can I set this up on google dfp small business.
The frequency cap is per user we don't want it to be per user. Can someone please advice.
Many thanks
There is one workaround and one option inside DFP to make this work:
Create an order with a single line item with a running time of just one month and your monthly impression goal.
You can then copy this single line item 11x times with it's creatives in to the same order and adjust only the start/-enddate.
The ad unit code, etc. can remain the same in this setup.
If you want to rely on DFP's built in features you can choose a price priority line item, which would allow you to set a daily impression goal. You would need to target this line item type to a special ad unit in order to work. The daily impression goal is of course the amount of impressions you want to serve per month, divided by 30.5.
This can be easily done.
Go to your line item
Go down to "Adjust Delivery"
Tick "Frequency"
In the first field box, add "50,000" to denote your impressions limit and then in the 2nd box, leave it as "1" and then change the default "Day" setting to "Month".
Save
This will allow the line to serve to a limit of 50,000 max per month.