Hi all,
We are wondering how to go about reporting on the Work Item Description, as well as some other (3 or 4) custom defined ntext fields in TFS for one team project. As far as we understand it, the recommended way to go about this is to mark the fields as reportable, and then use the TFSWarehouse for reports. We have a team which wants to get read only access to the operational databases to run reports against them, and we don't think that this is a good idea (and reading Charles Sterling's blog confirms this as well - http://blogs.msdn.com/charles_sterling/archive/2006/11/06/creating-new-t fs-reports.aspx) We've since found out though that you can't mark these fields as reportable, since they are "Plain Text" type. Does anyone have any guidance or experiences with getting the work item description and other plain text fields out to people in a reportable way? Alternatively, does anyone report directly against the operational data stores? If so, what is the best way to go about setting up report data sources to have this access, without exposing all of the data out too much? To put this in context, we're not really taxing the server, there are approximately 20 - 30 people using the TFS server at the moment, with scope for perhaps up to around 100 in future. Of this, only around 20 are actually developers using it via Visual Studio, and of those, only around 10 are working on the project in question. Cheers, Matt Taylor Senior Systems Development Officer Software Portfolio Group | Information & Facilities Management | Organisation Services & Strategy Queensland Department of Housing Ph: 383 60118 Email: [EMAIL PROTECTED] WARNING * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This email (including any attachments) may contain legally privileged and/or confidential information and maybe protected by copyright and/or the subject of moral rights. You may use this email and/or the attachments if you are the person(s) it was intended to be sent to and if you use it in an authorised way. Any unauthorised use of this material, in particular in any form of disclosure, modification, distribution and/or publication of this email and/or the attachments, is prohibited. If you have received this email in error, please notify the sender immediately, delete the email and attachments and any copies of it for your computer system network, and destroy any printed or electronic copies taken. Any legal privilege and/or confidentiality is not waived or destroyed by that mistake. Unless stated otherwise, this email represents only the views of the sender and not the views of the State of Queensland. The State of Queensland does not accept any responsibility for any loss or damage that may result from reliance on, or the use of, any information contained in this email and/or attachments. Unless specifically stated, this email should not be construed as a purchase order, nor as an arrangement to provide a service. It is your responsibility to ensure that this email and any attachments do not contain and are not infected by computer viruses, defects or interference by third parties or replication problems (including incompatibility with your computer system network). * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * OzTFS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by www.readify.net
