Invoking the date picker on a Confluence page does nothing
Platform Notice: Data Center Only - This article only applies to Atlassian apps on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Confluence does not render a date picker when either:
Entering a // within a page.
Invoking the Date macro from the menu.
Diagnosis
Within the atlassian-confluence.log file, an entry like the following will be present shortly after start up:
2026-09-09 08:51:52,609 ERROR [ThreadPoolAsyncTaskExecutor::Thread 20] [plugin.osgi.factory.OsgiPlugin] onPluginContainerFailed Unable to start the plugin container for plugin 'com.atlassian.confluence.plugins.confluence-inline-tasks'
org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'inlineTasksRebuildImportFinishedListener': Unsatisfied dependency expressed through constructor parameter 1: Error creating bean with name 'inlineTaskService' defined in URL [bundle://b16d644f-02e0-43cf-b1a2-4bc9e3e0f6e4_79.0:0/META-INF/spring/spring-components.xml]: Unsatisfied dependency expressed through constructor parameter 12: Error creating bean with name 'tasksFinderViaSearchIndex': Unsatisfied dependency expressed through constructor parameter 0: Error creating bean with name 'inlineTaskSearchIndexAccessor': Failed to instantiate [com.atlassian.confluence.plugins.tasklist.report.searchindex.InlineTaskSearchIndexAccessor]: Constructor threw exception ...
Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'inlineTaskService' defined in URL [bundle://b16d644f-02e0-43cf-b1a2-4bc9e3e0f6e4_79.0:0/META-INF/spring/spring-components.xml]: Unsatisfied dependency expressed through constructor parameter 12: Error creating bean with name 'tasksFinderViaSearchIndex': Unsatisfied dependency expressed through constructor parameter 0: Error creating bean with name 'inlineTaskSearchIndexAccessor': Failed to instantiate [com.atlassian.confluence.plugins.tasklist.report.searchindex.InlineTaskSearchIndexAccessor]: Constructor threw exception ...
Caused by: com.atlassian.confluence.internal.search.v2.lucene.LuceneException: java.nio.file.NoSuchFileException: /var/atlassian/application-data/confluence/index/task_report_index/segments_ks9 ...
at com.atlassian.confluence.internal.search.v2.lucene.LuceneConnection.upgradeIndexIfNecessary(LuceneConnection.java:613)
at com.atlassian.confluence.internal.search.v2.lucene.LuceneConnection.ensureCorrectIndexFormat(LuceneConnection.java:598)Based on this error, the Inline Task plugin (eg. com.atlassian.confluence.plugins.confluence-inline-tasks), which is responsible for the data picker functionality, did not properly start up due to a corrupt Lucene index: task_report_index.
As a confirmation, click on the Admin console cog > Manage apps > System and observe that the Confluence Inline Tasks plugin is disabled.
Cause
The date picker feature is provided by the bundled Confluence Inline Tasks system plugin (com.atlassian.confluence.plugins.confluence-inline-tasks), which fails to start and remains disabled if its local Lucene index directory (<confluence-home>/index/task_report_index/) is corrupted or missing segment files, resulting in an UnsatisfiedDependencyException during startup.
Solution
The task_report_index specified above needs to be deleted so that Confluence can regenerate it:
Stop Confluence on all nodes.
Delete and/or move into some other non-Confluence folder the following folder on both nodes: <confluence-home-folder>/confluence/index/task_report_index/
Start Confluence. The plugin should initialize a fresh index and come up ENABLED.
Optionally rebuild task index content afterwards via Admin → Content Indexing
Was this helpful?