Is there a way to configure the burndown chart in a way where I can change the Completed state to one of the middle states on my kanban board?
Unfortunately, this is not possible at the moment and under development by the azure team in line with requests.
You can track the process at here: https://developercommunity.visualstudio.com/t/allow-burnupburndown-charts-to-include-resolved-wo/578309
Related
In order to save expenses in Azure DevOps, I'm trying to scale the resources, which can scale depending on the requirement. Team leads will update the resource requirements in SharePoint, and the runbook needs to be executed with SharePoint datat. Team leads will update the resource requirements in SharePoint, and the runbook needs to be executed with SharePoint data. If such resources are not required on weekends but must be operational on weekdays, they should be stopped or reduced in size. I need to use automation to do it for all of the VMs and App Services at a subscription level every Friday. If there is a method to automate this procedure using PowerShell.
I'm glad to receive input. Thanks in advance.
I'm looking for feedback on Start/Stop VMs and Scaling Azure App Services. On weekends, the same may be said for other relevant resources. How can we accomplish this with Azure PowerShell?
The best way to do is by using 'Azure Automation Runbook' scheduled to run every specified day or date by time. To target the VM's, Azure Tags will be much helpful.
Your script must check:
A VM has a specific Tags (e.g., StopVM:Friday 11:00PM)
Maintenance Enabled in your monitoring solution
VM is stopped already or not.
Backup required?
Confirm the VM is Deallocated (not stopped)
Auto-Shutdown option is also available to do this activity.
Because sometime all you need is a quick and dirty way to save money :
And if you wan't to build something there's an API to shutdown and start VMs
I have a project that I need to manage from end to end so that I track user stories from inception through to meeting the definition of ready and track that on a Kanban board.
I then want to have a backlog of items which meet the definition of ready from which I can sprint plan and then track these items from sprint backlog through development, test and finally to done using a scrum board.
I have looked through the organisation settings, but it seems that when you set the board process all boards use the same process.
is this possible in Azure DevOps?
I see that in Azure Devops the billing account is set per organization. So, I can do a cost analysis per organization. Is it possible to do the same thing on a project level with labels and etc? I have checked but I couldn't find any labeling for the projects.
I want to see what is the exact cost of each project based on users, pipelines, parallel jobs costs.
I could not find any billing per project as your question states.
As an alternative or workaround ( I'm not saying this is an ideal solution) you could separate your projects in organizations in order to be able to bill them separately.
Just in case here is the link about billing per organization and here is the link for Billing overview for Azure DevOps in case it may give you some more insights.
Is it possible to do the same thing on a project level with labels and etc?
For this issue , I am afraid this is currently not possible in azure devops . Until now, billing only exists in organization level.
You could add your request for this feature on our UserVoice site , which is our main forum for product suggestions.After suggest raised, you can vote and add your comments for this feedback. The product team would provide the updates if they view it. Thank you for helping us build a better Azure DevOps.
In addition, for detailed information about billing, you can refer to this document.
I love Azure DevOps and burndown charts even more, I really do.
So much that I am trying to substitute the legacy Excel Spreadsheet with DevOps.
While the default burndown chart takes into account all the members of a team, I'd need to get one for each of the team members.
Is there a way to do it ? And if there is more than one, which is the best ?
Following the instructions here it could come to my mind to create a new team for each team member... but it sounds stupid. Anyone had the same requirement before ?
Currently, there is no out of the box way to see burndown chart of individual team member. Users have requested this feature and is currently under review.
Not out of the box. However if you have Power BI there is a plug in for Azure Dev Ops that is currently in beta.
This essentially will give access to the raw data exposed via APIs in Azure Dev Ops.
Once connected multiple burndown charts could be created or have a static filter for each one. Or alternatively create page filters so you could quickly filter by team member. The trick here will be to get the data model correct for what you are trying to accomplish.
I have arm template to recreate resource group with resources and their settings. This works fine.
Use case:
Some developer goes to azure portal and update some settings for some resource. Is there a way how to get exact changes that can be applied to my template to take these changes in effect? (Update template in source control)
If I go to automation script in resource group I can see all resources but my template in source control is different (parameters, conditions, variables, multiple templates linked together ...). I can't see on first look what changes were done and I can't use any diff.
Maybe I missed completely something but how are you solving this issue?
Thanks.
It is not easy to see any changes to resources by comparing templates from within the portal. Best practice is to always use ARM templates (and CI/CD pipelines) to deploy ARM templates to provision resources. Keep these ARM templates under source control to track them.
Further than that, I think you have two main options to track these changes:
1) You can use the Azure Activity Log to track the changes. The Azure Activity Log is a subscription log that provides insight into subscription-level events that have occurred in Azure. This includes a range of data, from Azure Resource Manager operational data to updates on Service Health events.
2) Write a little intelligent code against the Management Plane API. A good starting point is https://resources.azure.com/subscriptions. You could write a little extract that pulls all your resources out daily and commits them to a git repo. This will only update for changes to templates. You can then analyse the delta as or when you need.
Conceptionally, the developer should never 'go[es] to azure portal and update some settings for some resource', except for his own development / unit testing work. He then should produce an updated ARM template for deployment in the TST etc environments, and document his unit-tested changes with the new template. If his update collides with your resources in TST he will probably come to you to explain his changes, and discuss the resolution.