@albert-github turns out there is sth called xslt xml transformation file. Just snippet below is enough to generate

<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

    <xsl:output method="xml" encoding="UTF-8" indent="yes"/>

    <xsl:template match="/">
         <xsl:for-each select=".//memberdef">
            <xsl:if test="xreftitle or .//xreftitle">
                <JamaReq>
                <xsl:text>&#10;</xsl:text>
                <definition><xsl:value-of select="definition"/></definition>
                <xsl:text>&#10;</xsl:text>
                <xsl:copy-of select="location"/>
                <xsl:text>&#10;</xsl:text>
                <xsl:for-each select="inbodydescription/para/xrefsect/xrefdescription/para">
                    <JamaApi><xsl:value-of select="."/></JamaApi>
                    <xsl:text>&#10;</xsl:text>
                </xsl:for-each>
                </JamaReq>
                <xsl:text>&#10;</xsl:text>
            </xsl:if>
         </xsl:for-each>
    </xsl:template>

</xsl:stylesheet>

Looks like your description in #11567 (reply in thread) is a bit truncated, please complete it.

• Were you able with the xslt sheet, of which you gave a snippet, to import the doxygenXML data into JAMA?
• Where can the complete xslt sheet be found?

Would you like me to open PR? Let me know where should I put it. I ll put screenshots regarding importing procedure in PR

Please first explain what you have done and answer the questions as indicated in #11567 (reply in thread)

The screenshots regarding importing procedure can be put into this discussion.

English is my second language. Sorry for mistakes

So unfortunately JAMA's import tool is not powerful enough to handle what we are trying to with this automatic tracing. But their rest API are very easy to use. Since doxygen is doing the heavy lifting of parsing source code, pushing some data to server is trivial now.

jama.txt

Example C Code:

void blinkerTurnSignal(void)
{
    //! @Jama{1234} v1 while turn blinker is on, one of the light components failed. blink frequency increased to 2 times faster.
    if(isThereFault == TRUE) {
        // blink 2 times faster
        blinkFrequency *= 2;
    }
}

XSLT converts to this format which you could push it to JAMA Servers

<Jama>
	<JamaRequirement>
		<definition>void blinkerTurnSignal(void)</definition>
		<Location>file:blinker.c	line:20	column:6</Location>
		<JamaApiId>1234</JamaApiId>
		<JamaVersion>v1</JamaVersion>
		<JamaDescription>while turn blinker is on, one of the light components failed. blink frequency increased to 2 times faster. </JamaDescription>
	</JamaRequirement>
</Jama>

How it looks on Jama

Since system requirements now have links to code. We could do analysis of what percentage of system requirements are implemented in actual code