-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Medium
-
None
-
Affects Version/s: 10.2.7, 10.2.10
-
Component/s: Content - Tasks
-
None
-
4
-
Severity 3 - Minor
-
51
Issue Summary
Tasks created on child pages that inherit "Can view and edit" restrictions from a parent page do not appear on the assigned user's profile under their task list, even though the user has the necessary permissions. This affects task visibility and tracking for users working within restricted page hierarchies.
Steps to Reproduce
- Create any user (can be replicated with admin also)
- Create a parent page with restrictions allowing the user individually with ‘Can view and edit’ permissions
- Create a child page and add a task tagging the same user
Expected Results
The task should appear in the user’s Profile → Tasks
Actual Results
The task doesn’t appears in the user’s Profile → Tasks
Attached Replication Video:
The below warning is thrown in the atlassian-confluence.log file:
WARN [Caesium-1-1] [searchindex.indexmanagement.indexqueue.IndexQueueProcessorImpl] lambda$processJournalEntries$1 Failed to process the next batch of task org.hibernate.HibernateException: Failed to find org.hibernate.Session from the current thread
atlassian-confluence-index.log
WARN [Caesium-1-1] [confluence.impl.journal.DefaultJournalManager] handleFailedEntry Entry in journal [task_report_index] with ID [xxxx] has reached the maximum try times (3), skipping it
Workaround
- Perform a space/content reindexing and the task will appear. However creating a new task again the same way, the issue will occur.
- Add the dark feature 'confluence.task-report.use-database-for-reports'. This will force Confluence to always retrieve the Task Lists from the database instead of relying on the Task Report Index.