My company is using Netsuite to track defects and requests. I would like to use Visual Studio online to keep track of my sprint and port the defects and requests into the backlog. Is this possible?
You may be able to use VSO's Service Hooks.
Related
Unable to create a Requirements based Test Suite using TFS .NET API nor the REST API in TFS 2015. Using the TFS web portal this is possible.
I understand the reason why the API's fail, which is that the EPIC work items I'm using are not in the "Requirement Category." However, the TFS web portal lets me use these same EPIC work item as the requirement for a requirements based test suite. Go figure?
Since the project I'm working on involves a Fortune 500 company it is no simple feat to add EPICs to the "Requirement Category." Since the TFS web portal uses some kind of work-around I'm wondering if someone can clue me in as to how it's being done, and if I can take advantage of it using the .NET or REST APIs.
Thanks
I could reproduce your issue on my side. According to the REST api of Create a test suite, parameter requirementIds supports categories of requirement type are: Epic, Feature, Requirement, and Bug. But REST api can not support Epic work items actually:
I have report a feedback at website below, we will get response soon:
https://developercommunity.visualstudio.com/content/problem/231035/creating-requirement-based-test-suite-fails-throug.html
To be clear, I am not asking about about version control, or capabilities of the back end, but the front with the tie in with the interested parties. (Contributors, Viewers, Users)
Would those that work with both TFS and VSTS, would you say that TFS and VSTS have all the same "Visual" components (comparable version coalition) with the difference of placement being:
TFS is to SERVER (Designated/Local Server)
VSTS is to CLOUD (Online servers)
I have read all of the comparable but none talk to this aspect that I can find.
i.e. do you see the same portal pages and project counter parts in TFS as you do in VSTS?
Suggest you first go through the official doc from MSDN: Understand differences between VSTS and TFS
VSTS is the cloud offering that provides a scalable, reliable, and globally available hosted service. It is backed by a 99.9% SLA,
monitored by our 24-7 operations team, and available in local data
centers around the world.
Team Foundation Server is the on-premises offering built on a SQL Server backend. Organizations typically choose on-premises TFS when
they need their data to stay within your network, or they want access
to SharePoint sites and SQL Server reporting services that integrate
with TFS data and tools.
Fundamental differences between TFS and VSTS
Scope and scale data
Authentication
Users and groups
Manage user access
Security and data protection
Key feature differences between VSTS and TFS
Process customization
Reporting
You could review the details for the front with the tie in with the interested parties. (Contributors, Viewers, Users)
Back to your question, *do they have the same Project pages to display to users? * It's basically the same, most new features are released to Visual Studio Team Services first and are integrated into Team Foundation Server with a bit of a delay. Some features are available in VSTS which depend on cloud resources, so they're not likely to move to TFS anytime soon.
Also take a look at this similar question: Future of TFS vs VSTS
I need to access TFS outside the domain. I thought that I can publish the TFS through WAP, but it seems that TFS does not support the authentication used by ADFS. Any other idea on how to do this? Thanks.
TFS does not support ADFS, there is a user voice here, you can go and vote it up or summit a new user voice to achieve it in future.
However, to access TFS outside the domain you can try below items:
Try to provide access to TFS over a virtual private network (VPN).
Try to provide access to TFS through a reverse proxy such as Microsoft Internet Security and Acceleration (ISA) Server.
Try to host your TFS server on an extranet.
You can reference this article : Providing Internet Access to Team Foundation Server
Besides, you can use Visual Studio Online, connecting remotely is a good option. And if you are doing any cloud work it integrates nicely.
This link (http://msdn.microsoft.com/en-us/library/ms252507(v=vs.100).aspx) from Microsoft describes various domain \ work group combos for your reference.
I am a part of the team where the TFS 2012 is being used. I am not sure I can get SQL access to the TFS Warehouse. So like to know if it is possible to reconstruct the TFS Warehouse or Analysis service on my local machine. Is there any web services exposed via TFS 2012? Does it need any special permission.
I looking for TFS Analysis database as per http://msdn.microsoft.com/en-us/library/ms244699%28v=vs.110%29.aspx
After lot of research found that it is not possible. The main missing information is the relationship between the items. like User story to tasks relationship. Without this we can not do much.
We're using TFS for source control and are trialling using the TFS work item tracking. I am trying to find out, is it possible for people who don't have visual studio installed to access, create and edit work items via a browser based user interface?
Our technical support team need to be able to use work items. TFS work items won't be suitable for our company if the support team and project managers can't get sufficient access.
I'm not familiar with how the licensing works either. If there is a way for non visual studio users to use TFS work items, will they need a license?
The are a number of choices (most costing money):
Team System Web Access
Team System Web Access (formerly known as TeamPlain) is a Web interface to Visual Studio 2005 Team Foundation Server. Team System Web Access is available as a free download for existing Team Foundation Server users, and will be incorporated into a future release of Visual Studio Team System.
Work Item Only View
Team System Web Access provides a work item only view that restricts functionality so that you can create and view only your own work items. This view is designed to facilitate working with Team Foundation Server when you do not have a client access license (CAL). You do not need a CAL to create new work items or to view and update work items that you created. The work item only view restricts functionality so that you are in compliance with this aspect of the Team Foundation Server end user license agreement. For more information, see Visual Studio Team System 2008 Licensing White Paper.
Outlook integration (from Brian Harry's blog)
Integration of Team Foundation Server work items into the Outlook user experience continues to be a popular area for innovation. Just recently an author sent me mail about a new one called Wit-It! that enables work item forms to be easily opened from TFS work item change notifications. It's not entirely unlike configuring links to Team System Web Access from event notifications but it uses local rich client UI that some will like better.
There are several other Outlook extension offerings out there with varying levels of completeness. If it's an area that iterests you, you can also check out:
TeamExpand
TeamLook
TeamCompanion
And I appologize if I left any out. As I say, clearly there is a lot of interest here and some creative people.
Team System Web Access is a good web-based option for non-visual studio users.
There should be a web interface, both a website and a SharePoint portal that gets installed with TFS. The portal will let you get to the documents and view some reports. The website will let you work with the documents, the source control, work items, and bug reporting.
As far as licensing goes, a full-blown TFS user requires a TFS CAL (in addition to the normal Windows Server CAL).
However, for particular types of 'light' users a TFS CAL might not be required (I'm not sure, but I'd think that a Windows Server CAL would still be required). See http://blogs.msdn.com/bharry/archive/2007/11/23/tfs-licensing-change-for-tfs-2008.aspx for some details.
As always, MS server application licensing requirements are often quite complicated - you will need to do your own research (probably in consultation with MIcrosoft) to determine your actual licensing requirements.