Hi,
I am using Aura Table Filter and Yogi Requirement.
When I use Yogi Requirement to create my requirement ID's in the first column then the requirement IDs no longer appear in the Aura table filter.
It works fine when I do not use Aura Table Filter.
Could you please advise on how to fix the issue?
Thank you
Hi Elise,
This usually happens because the Aura Table Filter macro doesn’t automatically recognize dynamically generated content (like IDs or values created by another macro such as Yogi Requirement).
Here are a few things you can try:
Rebuild or refresh the table data after the Yogi macro runs.
Try clicking inside the Aura Table Filter → Edit → Save again.
This forces it to re-scan the table content and often restores missing columns.
Check the rendering order.
Make sure the Yogi Requirement macro is inside the table before applying the Aura Table Filter macro.
Aura filters only the visible table data when the page is loaded — so if Yogi generates content after load, Aura won’t detect it.
Alternative approach:
Convert or copy the generated requirement IDs as plain text (instead of live macro content). Aura will then treat them as standard table cells and filter correctly.
If none of these solve it, it might be a macro rendering conflict, and contacting Aura support would be the best next step — they’re very responsive and can confirm if the two macros are fully compatible in your version.
Hi Elise,
This usually happens because the Aura Table Filter macro doesn’t automatically recognize dynamically generated content (like IDs or values created by another macro such as Yogi Requirement).
Here are a few things you can try:
Rebuild or refresh the table data after the Yogi macro runs.
Try clicking inside the Aura Table Filter → Edit → Save again.
This forces it to re-scan the table content and often restores missing columns.
Check the rendering order.
Make sure the Yogi Requirement macro is inside the table before applying the Aura Table Filter macro.
Aura filters only the visible table data when the page is loaded — so if Yogi generates content after load, Aura won’t detect it.
Alternative approach:
Convert or copy the generated requirement IDs as plain text (instead of live macro content). Aura will then treat them as standard table cells and filter correctly.
If none of these solve it, it might be a macro rendering conflict, and contacting Aura support would be the best next step — they’re very responsive and can confirm if the two macros are fully compatible in your version.
Welcome to Atlassian Community!
As suggested by @Jason U we suggest you to raise a support request with the vendor directly who can better assist you the conflict in integration of these apps on your site.
Here is the direct URL where you can raise a support request as well: https://marketplace.atlassian.com/apps/1212523/requirement-yogi-requirements-management-for-confluence?hosting=cloud&tab=support.
Best Regards,
Vishalakshi Narayanaswamy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.