Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Troubleshooting errors with a story template

Updated on January 14, 2022

When you import your stories in bulk to Agile Workbench, you might encounter errors. Typically, errors stem from an invalid story template file type or information missing in the story template.

The template has an invalid file structure or an invalid file type

Import of stories fails because the file that you upload is in a format different from .xlsx. The Import Stories modal dialog box displays information that no file is chosen.

  1. In the navigation pane of App Studio, click Overview.
  2. In the Application profile section, click Manage.
  3. In the header of the Application profile section, click ActionsImport Stories.
  4. In the Import Stories dialog box, click Download the template to save an .xlsx file to your local machine.
  5. Open the file.
  6. Copy the information from your original template to the relevant columns in the file.
  7. Save the file but do not change its format.
  8. In the Import Stories dialog box, click Choose File.
  9. Navigate to the location of your story template, and then click Open to upload the file.

Stories fail import

When you import stories, the import fails. The Application profile header displays a message with a number of failed stories, as shown in the following figure:

Failed import message
Application profile with a message about fail stories import.
  1. On your local machine, navigate to your story template.
  2. Ensure that you provide a value for all stories in the Name column.
  3. Save the file but do not change its format.
  4. Restart the import.

    Have a question? Get answers now.

    Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

    Did you find this content helpful?

    Want to help us improve this content?

    We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

    Close Deprecation Notice
    Contact us