Report formatting issue when requirements imported from Excel

Wednesday, July 13, 2022
Avatar

It seems that when importing requirements from Excel (SpiraImportTemplate2010) there is some hidden formatting that apperas only in the Requirements report, and “Remove Format” button is disabled in Spira for the requirement.

How i get requirements in the report:

RQ:2230A Contratada DEVE disponibilizar o código-fonte final do software.
 
RQ:2231

A Contratada DEVE fazer um workshop de repasse de tecnologia sobre estrutura e organização do código fonte e uso da solução desenvolvida.

RQ:2232

Testando criação de requisito, ao invés de importar no Excel.

Exmplanation:

RQ:2232 was created directly in Spira. Format in the report looks good.

RQ:2231 was created by import via Excel, but after this was edited in Spira, just to cause another SAVE, no real change. Note: The “Remove Format” button was disabled in the requirement in Spira.

RQ:2229 and 2230 were created by import via Excel. There seems to be a formatting issue because there is no space between “RequirementId” and “Description” but the “Remove Format” button is also disabled in the requirement in Spira.

My report code:

  <xsl:template match="/RequirementData">

    <xsl:for-each select="Requirement">

      <div>

        <xsl:attribute name="style">

          margin-left: <xsl:value-of select="string-length(IndentLevel)*3"/>px;

        </xsl:attribute>

        <xsl:if test="IsSummary='True'">

          <div class="Title2">

            <xsl:value-of select="Name"/> - RQ:<xsl:value-of select="RequirementId"/>

          </div>

          <div class="Description">

            <xsl:value-of select="Description" disable-output-escaping="yes"/>

          </div>

          <br />

        </xsl:if>

        <xsl:if test="IsSummary='False'">

          <xsl:attribute name="style">

            padding-left: <xsl:value-of select="string-length(IndentLevel)*3"/>px;

          </xsl:attribute>

         <!-- <div class="Title3">

            RQ:<xsl:value-of select="RequirementId"/>

          </div> -->

          <p></p>

           <b>RQ:<xsl:value-of select="RequirementId"/></b>

           <xsl:value-of select="Description" disable-output-escaping="yes"/>

        </xsl:if>

       

        <br />

2 Replies
Wednesday, July 13, 2022
Avatar
re: Renato.certi Wednesday, July 13, 2022

Hi Renato

Please can you submit a support ticket for this: https://www.inflectra.com/Support/Ticket/List.aspx

Regards

David

Thursday, March 30, 2023
Avatar
re: inflectra.david Wednesday, July 13, 2022

When importing requirements from Excel, it's possible to encounter formatting issues in the report generated. Here are some potential causes and solutions:

  1. Formatting inconsistencies: If the formatting of the requirements in Excel is inconsistent (e.g., different fonts, sizes, or colors), this can cause issues when importing the data into the report. To fix this, make sure that all requirements in the Excel file are formatted consistently.

  2. Missing data: If the Excel file contains missing data for certain requirements, this can cause issues when generating the report. Check the Excel file to ensure that all requirements have complete information.

  3. Improper data types: Ensure that the data types in the Excel file are compatible with the report generation tool. For example, if a column is intended to contain numeric data, make sure that all values in that column are numbers.

  4. Character encoding issues: If the Excel file contains non-standard characters or character encoding issues, this can cause issues when generating the report. Make sure that the character encoding in the Excel file matches the encoding expected by the report generation tool.

  5. Software compatibility issues: Different software tools may have different requirements for importing data from Excel. Make sure that the report generation tool is compatible with the version of Excel being used, and that any necessary plugins or add-ons are installed.

  6. Column width issues: Ensure that the column widths in Excel are wide enough to accommodate the data being imported. If the columns are too narrow, the data may be truncated or lost during the import process.

By addressing these potential issues, you should be able to import requirements from Excel and app development company generate a report without formatting issues.

Spira Helps You Deliver Quality Software, Faster and With Lower Risk

And if you have any questions, please email or call us at +1 (202) 558-6885

 

Statistics
  • Started: Wednesday, July 13, 2022
  • Last Reply: Thursday, March 30, 2023
  • Replies: 2
  • Views: 435