Overloaded functions are mixed when their arguments have template with object in other namespace

[st-masa]

Describe the bug

Assuming these structs are defined in namespace aa.

namespace aa {

/**
 * @brief Struct1
 */
struct Struct1
{
    int struct1_0;
    int struct1_1;
};

/**
 * @brief Struct2
 */
struct Struct2
{
    int struct2_0;
    int struct2_1;
};

}

And aliases of them are defined like this in namespace bb.

namespace bb {

/**
 * @brief alias of Structt1 in bb
 */
using Struct1 = aa::Struct1;
 
/**
 * @brief alias of Structt2 in bb
 */
using Struct2 = aa::Struct2;

}

The documentation of these overloaded function are mixed into one.

/**
    * @brief   FunctionExample (overload 1)
    *
    * @param[out] arg1 Struct1Type argument
    * @param[in] arg2 int argument
    *
    * @return return value
  */
int FunctionExample(Struct1Type arg1, int arg2);

/**
    * @brief   FunctionExample (overload 2)
    *
    * @param[out] arg1 Struct2Type argument
    * @param[in] arg2 int argument
    *
    * @return return value
  */
int FunctionExample(Struct2Type arg1, int arg2);

Screenshots

To Reproduce
Extract unifiedOverloads.zip and run doxygen.

$ ce ./unifiedOverloads
$ doxyen ./DoxyFile

Expected behavior

Two overloaded functions are documented separately.

Version
Confirmed with v1.12.0. But can be reproduced with earlier versions.

[st-masa]

When #if statement is set to false, functions are separately documented.

#if false // if true, FunctionExample overloads are mixed.

Struct1Type and Struct2Type are chagned to use the following aliases under bb.

/**
 * @brief alias of Structt1 in bb
 */
 using Struct1 = aa::Struct1;
 
 /**
 * @brief alias of Structt2 in bb
 */
 using Struct2 = aa::Struct2;

[albert-github]

Maybe also related to #3760 (though I still see the problem in the current master version 1.13.0 (39744a6))

[doxygen]

@st-masa Please verify if the referenced commit fixes the problem for you. Do not close the issue, this will be done automatically when the next official release becomes available.

[st-masa]

@doxygen Sorry for my late reply. I confirmed the problem was fixed.
Thank you!

[doxygen]

@st-masa While preparing for the next release, I unfortunately discovered some regression because of this fix. For now, I decided to disable the fix and look for a better solution after 1.13.0 is released.

[st-masa]

@doxygen Understood. Looking forward to the solution. Thank you.