How can we improve Team Services?

Add HTML field editing to Excel for Work Items

When viewing/editing TFS work items in Excel, fields that are HTML type fields are read-only for existing work items. See the following blog: http://blogs.msdn.com/b/team_foundation/archive/2010/05/26/change-in-html-field-behavior-in-the-2010-tfs-excel-integration.aspx

Please modify TFS or Excel to allow cells to contain and allow editing of this HTML data in the next Visual Studio release.

7 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Chris BeersChris Beers shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    We don’t want to allow the user to modify the actual HTML in Excel. We have considered this scenario, but we think that the validity of the data is more important than the bulk update scenario.

    Ewald Hofman
    Program Manager, Team Foundation Server

    5 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • John HenckelJohn Henckel commented  ·   ·  Flag as inappropriate

        You are wrong. Bulk upload is much more important than ensuring validity. The users of bulk upload are obviously power users. They know how to validate their own data. They don't need to be coddled by the tool. i agree with other posters, we NEED a minimal set of HTML tags. How about bold and line breaks. How about markdown, for crying out loud! Using the web interface to edit dozens of Stories is too tedious.

      • Ann NeelAnn Neel commented  ·   ·  Flag as inappropriate

        Authors need to maintain user stories in a format that is readable by the business. For those of us working in an IT shop in a non-IT industry, we cannot expect the business to use TFS; they need a Word document.

        There is a work-around for carriage returns within a user story pasting to multiple rows in Excel, as found here: http://superuser.com/questions/747197/how-do-i-copy-word-tables-into-excel-without-splitting-cells-into-multiple-rows
        But this doesn't solve the other formatting issues of bolding, bulleted or numbered lists, etc.

        With these formatting issues, the bulk upload and download with Excel still requires us to essentially key user stories in two places. You should either fix the formatting lost in the bulk download and upload, possibly by interfacing with Word tables instead of Excel, or you need to create an output document from TFS for user reading.

        Declining such a request forces us to look for a third party add-on tool or to ditch TFS for a competitors tool. This is lost business, short-sighted at the very least.

      • Tony DanzaTony Danza commented  ·   ·  Flag as inappropriate

        This is insane logic. This effectively blocks my ability to bulk upload requirements into TFS, since many are multi-line.

      • Peter JohnsonPeter Johnson commented  ·   ·  Flag as inappropriate

        Please consult with the community about this one. I think the data is invalid if you strip the most basic formatting from the text being edited.

        Can you at least maintain line feeds (New Lines, Carriage Returns) in the formatting?

        Ideally it would minimally support Bold, Italic, Underline, Line Feeds.

        The behavior is very inconsistent, on first bulk loading of the data line feeds are maintained but on subsequent edits it strips all of the line feeds out.

      Feedback and Knowledge Base