It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How does the Glossary Plugin work with the Confluence search?

I'm wondering why I can't find any of the terms in my glossary through a full-text search.

The main reason why I want to know that is, because I want to make the glossary items available in a connected SharePoint platform (using the Search Connector Add-on). But, if even Confluence doesn't find the terms in the first place, SharePoint (or the Search Connector) will not be able to do so as well.

How can I make sure, that the glossary items, i.e. the content of the specific macros that contain those items, are searchable?

best regards,


6 answers

Hello Paul, I believe you already been through the plugin docs where it reads that items should be inserted through the plugin interface. Now would it be possible to give a example with actual words, so anyone that attends to this thread can reproduce?

Hi Guilherme,

thank you for your reply. I think I didn't make myself clear enough...

Let me try to explain the sitiuation again: I have a list of several (dummy) entries in my glossary. For letter 'a' I added random abbreviations, e.g.  ABK, ABC, ACE, and so on. Every abbreviation or akronym has a description of its meaning also added using the glossary term macro (or the add term function in the glossary view). When I now use the basic Confluence Search, I cannot find any of these abbreviations/akronyms unless it is mentioned in the description.

What I want to know is, why I don't find the terms using the full-text search and how I can convince Confluence (or the Glossary Add-on) to show them in my search results.




@Anis Othman [Spectrum Groupe] Can you provide any details on the search integration of glossary items? Best regards, Paul

any answers?

bump - I don't understand why the 'search term' box  only allows you to search name of the glossary entry and not also search its abbreviations, seems like a shortfall personally. I'd rather not make one glossary entry for every abbreviation (the only way to get the glossary to work properly today) forcing users to create duplicate entries. 

that said, i believe this might be because this component isn't designed to be a searchable glossary, but be a cross confluence lookup from other pages. however, i think it's naive to think that's the only use case your users are going to use a glossary for.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Confluence Cloud

Bring information from GitHub into Confluence

I’ve got a couple of questions for you. Do you write technical documentation? What about technical documentation that references code and files from GitHub? In this article you will learn how to in...

32 views 0 3
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you