The response I had from MS licensing was dated 30 May this year. I am not aware that anything has changed. If it has changed then I would love to know as we would resurrect this project.
On 20 August 2013 09:16, David Kean <david.k...@microsoft.com> wrote: > Grant, do you know if this is still true?**** > > ** ** > > *From:* ozdotnet-boun...@ozdotnet.com [mailto: > ozdotnet-boun...@ozdotnet.com] *On Behalf Of *Grant Maw > *Sent:* Monday, August 19, 2013 4:00 PM > *To:* ozDotNet > *Subject:* Re: Options for exposing TFS to customers and/or ticketing > system**** > > ** ** > > We have looked at this from the perspective of rolling our own. The idea > was to write an ASP.NET app that provided a way for our customers to come > in and log feature requests, report bugs and so forth via some interface > that we would create, and have the work items logged directly into TFS. We > also needed the ability for customers to see the status of any work items > that they have logged previously. **** > > **** > > What stopped us was the licensing - MS licensing told me that we would > need a TFS license for every customer. That policy effectively pulled the > shutters on the project so now we do it manually.**** > > ** ** > > On 7 August 2013 13:05, Preet Sangha <preetsan...@gmail.com> wrote:**** > > We are now big enough to require a ticketing system to manage customer > requests/tasks.**** > > ** ** > > Internally (8 of us) we use cloud TFS (visualstudio.com) and Office 365 > so a cloud based solution suits us better then us having to manage it. In > fact our whole infrastructure is slowly migrating to azure anyway.**** > > ** ** > > One of our customers has mentioned that another vendor as opened their > internal TFS to them so the solution might be as simple as that. **** > > ** ** > > However I thought I'd get some outside wise heads to comment on what they > might be doing or would recommend or perhaps not recommend. Before I head > down the road of evaluating systems.**** > > ** ** > > The main requirements are:**** > > ** ** > > 1. Avoiding duplication of data entry**** > > 2. Integration with VS2012 is a big 'would like' but not a show stopper as > we're to hapy to continue using TFS as our main entry point.**** > > 3. Prefer to pay someone else to manage it within reason**** > > ** ** > > We (people and clients) are world wide so local Asia/Pacific hosting etc. > is not a necessity in the slightest. **** > > ** ** > > ** ** > > What do you guys do?**** > > -- > regards, > Preet, Overlooking the Ocean, Auckland **** > > ** ** >
