51 votes3 comments · Azure DevOps (formerly Visual Studio Team Services) » Dashboards and Reporting · Flag idea as inappropriate… · Admin →
We are still considering how we would use VSTS to handle the 1,000's of projects created to serve our 200,000+ employee company. (ie: Many subscriptions vs centralised Project desk)
We are concerned that coordinating the large number of active projects will be a challenge.
If we can't hibernate the inactive projects, the clutter will multiply that challenge. Once developed, these projects go to operations & the dev team moves on.
Ideally we'd like an option to "zip up" the entire project & remove it from the projects windows.
We'd expect to add some kind of comments & tags that will help us find & rehydrate it in the future. Maybe via a separate "Archived Projects" window that helps with that.
It would be good if we can download a copy to keep On-Prem. Some execs are concerned about SAAS lock-in & want comfort that we could get our data back on-prem if required.
Ideally inside the "Archive" would be N separate "sub-archives"; The Source code, The Work-item history, the Build/Test/Release definitions, The configuration & the security/Users. As it is very likely a new team would exist by the time the business invested in enhancing the project. So need to be able to strip Users out & replace the team.
2 votes3 comments · Azure DevOps (formerly Visual Studio Team Services) » Release Management · Flag idea as inappropriate… · Admin →
The Build name does not have to have an Underscore "_" in front.
When you create a new Release the VSTS UI suggests a name, in a textbox, for you to edit as you desire.
By default, It adds an underscore at the front. Which I delete.
The solution to your issue is to check everything before hitting OK.
Hope this helps.
63 votes20 comments · Azure DevOps (formerly Visual Studio Team Services) » Work Item Tracking · Flag idea as inappropriate… · Admin →
We have begun the work to update our rich text editor control in all text fields on the work item form. This work will be our first step in creating a better editing experience on the form.
VSTS & TFS PM
Glad to hear it. Just getting a way to add Foreground, Background & Strikethru in the Descriptions & Repro Steps will be a big step forward.
(save us editing in Word & pasting into VSTS)
Would also be nice if the Wiki Editor had a Font Color picker too. Save manually adding HTML tags all the time.
253 votes25 comments · Azure DevOps (formerly Visual Studio Team Services) » Work Item Tracking · Flag idea as inappropriate… · Admin →
We understand the importance of this scenario, but during the investigation we determined that future additions to the process customization will have better support to implement a real blocked scenario. We are going to hold off of this one for a little bit longer and wait until that work is finished. That does not mean that we forgot about this at all!
As a work around you can add a blocked tag to your work items and use the tag coloring on the board to show these tags in red.
Agree. It is vital to quickly see what is stuck & not moving.