Wrong tags displayed for Q&A

[ErvinSzolke]

Hi,

I listed a specific Q&A tag page e.g. https://answers.sap.com/questions/metadata/24405/sbop-webdesktop-intelligence-clientserver.html

Scrolled down a little to this question,

as I was wondering at this point why I cannot see the tag "SBOP Web/Desktop Intelligence (client/server)" either above the title or at the bottom of the thread item (where I see only idt, universe, udt).

I clicked into the thread where I can see it

Sorry if this is already known.

Cheers,

Ervin

[audreystevenson]

Hi Ervin,

Let me check with the team.

Regards,

Audrey

[ErvinSzolke]

Small update: As I see right now the place where secondary- and user- tags were displayed is now empty, so the reported behaviour cannot be observed in its current form.

It can be however in a different form:

Example:

1. go to Tag page of "Using SAP.com" https://answers.sap.com/tags/486157991894093153608181816584982
   

   

2. At this point you are wondering why "ABAP Development" is listed

3. Open that question

4. You see that "Using SAP.com" is listed as Secondary tag.

   

5. However since this is not clear from the tag queue (see previous image attachmen), this is a little misleading and causes unwanted user experience.

Regads,

Ervin

[moshenaveh]

Hi Ervin,

Can you please post this in Idea place as this seems to be a requirement more than a bug? It seems to be the same behavior on the AEM tag page?:

http://www.sap.com/community/tag.html?id=907900296036854683333078008146613

It might clutter the display but I agree we need consistency across the tag pages.

Thanks a lot,

Moshe

[ErvinSzolke]

Hi Moshe,

Thanks for the response!

I am confused how this would this be an idea or requirement.

This looks to me a bug to be fixed and not a new feature, a new idea, a nice-to-have or any similar, but an existing feature that does not work as expected and confuses the end user and leads to misunderstandings.

Cheers,
Ervin

P.S. the link you sent points to SBOP, not to AEM but even if it there were more similar behaviours like the one I found, it still looks like a bug to me.