Hi, ngesin1378567119 we are unable to reproduce this issue, you might have a specific scenario that we have not covered/accounted for. If that is the case feel free to create a new ticket with your particular scenario so that we can look further into it.

Hi, this issue is not resolved for the Meeting notes template. The index page is not automatically generated when the Meeting notes template is used to create new wiki pages. Please prioritize and fix. Thank you!

THIS IS NOT RESOLVED!

How many meeting notes index tickets must it take before Atlassian works to resolve the issue?  Meeting Notes Index Page is not being auto generated.  There are no work arounds for that page.  Content Report Table just stacks the listed meetings.  Also it doesnt help new users with new Cloud instances to copy a Meeting Notes Index from another space.

Resolve this soon please.

Or a 'Page properties report' is better if you need it for product requirements

you can also add a 'Create from Template' macro button that simulates the create button you would have

The index page can be created manually as it is just a page with a Content Report Table Macro.

You can create a page and add a content report table macro, enter "meeting-notes" in the label field and pick a space to accumulate meeting notes from.

Example:

Is there any way we can create a "Meeting notes index" manually?

I'm also experiencing this problem and like others this is causing problems and is not a low priority problem.

I stumbled across this bug this morning when my meeting notes index pages wasn't created. It is definitely not a low priority here either.

Dear Atlassian, This is breaking your entire bluepriint setup since it is not possible to create the ready made index pages manually but they have to be re-done entirely by hand (unless you create a space where those index pages are automatically added as part of the space setup)

It saves a bit of time and this is one of the very few features I have come to actually like in Confluence (and there are are precious few of those). It is really a complete QA failure to have one of your "silent updates" completely kill this. It is definitely not a "minor" thing (as this bug is marked as) since it is virtually visible to close to 100% of your user base and the only workaround is to manually create index pages.

Please get this fixed ASAP!

(.. I sincerely hope this does not turn out to be yet another of the trivial bugs that takes 4+ years to even get a response for, let alone a fix.)

As a confluence champion at our company, this is a nuisance. I've just helped teams learn how to use blueprints in their spaces and the expected behavior is broken. I can understand needing time to complete an update but low priority is discouraging. Watching for a quick resolution.