As a VersionOne Product Owner, I would like the Import capability (both from Excel and the API) to honor the rich text data so that I don’t lose carriage returns, bullets, and all other formatting elements when importing my user stories and defects from other systems.  The whole string comes in as one big blob that I have to re-format.

Comments

  • More detailed user story:
    As a VersionOne Product Owner, I would like the Import capability (both from Excel and the API) to honor the rich text data so that I don’t lose carriage returns, bullets, and all other formatting elements when importing my user stories and defects from other systems.  The whole string comes in as one big blob that I have to re-format.

    This problem impacts all Product Owners and Scrum Masters (60-70 people, thousands of backlog items and defects) on an ongoing basis until we completely change from our in-house system to VersionOne. The project for changing the entire organization over, including support, will take at least one year. Even then, our in-house system will contain "attic" items that will be brought forward into VersionOne for planning as our customers raise issues.

  • Note that the import does honor HTML formatting. So, especially if converting from another system, if you can get your rich text fields in HTML format and import them that way, the formatting will be honored.

    A description field imported with the following content, for example, would display as formatted content when viewed in the application:

    This is a story I am importing. <br> It can have a bulleted list: <ul><li>like this</li><li>and this</li></ul>Isn't that <b>cool</b>?

  • When importing a test from Excel, any carriage return/line feed characters within appear to be replaced by the space character within the cell you are importing.

    Example:

    Steps (in Excel)
    1. Do this
    2. Do that

    Steps (in VersionOne)
    1. Do this 2.Do that

  • It is a huge hassle to add and remove HTML formatting when importing. I've written Excel macros to do this but it still messes up about as often as it works well. It would be much easier if this was just magically handled by VersionOne.

  • Agree with Simon B. The import should at least respect multi-line import values; without this, I have to manually edit every Description and similar HTML-based fields once they have been imported - with 500+ import items, that is a lot of wasted time!

  • Hey Version One folks - any update on this?

  • Hi Team,
    Can you please direct us towards API sample or Excel spreadsheet sample where *HTML* formatting is working. I am working with latest version still through API as well as Excel import, formatting is dishonored. It is quite painful and frustrating to do it manually for large number of items.

    I hope, somebody is listening at VersionOne Side.

  • +1 we import huge excel data and it just messes things up. Adding HTML tags to excel is pain. Why cant V1 handle this.