> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.2/minor-release/release8.1/release-notes/collaboration.md). # Collaboration ## Projects ### New & Improved #### Option to Update Child Tasks When Parent Task Is Moved to Done In Projects, when a parent task was moved to Done status, its child tasks remained in their existing statuses, creating inconsistent task hierarchies in which completed parent tasks could still have open child tasks, requiring users to update each child task manually. With this improvement, when a parent task with child tasks is moved to a Done status, the system displays a confirmation message asking whether all child tasks should also be moved to the same status. If confirmed, all child tasks are updated in bulk to match the parent task status. If declined, only the parent task status is changed. This enhancement is supported across the Kanban Board, List View inline updates, and the Task Shutter, ensuring consistent task-completion behavior and more accurate project tracking. ## Data Stories #### New & Improved #### Added No Borders Option for Tables in Data Stories In Data Stories, users could not hide table borders because the No Borders option was not available in the table formatting settings. This limited the ability to create cleaner and more presentation-friendly table layouts. With this improvement, a No Borders option is now available for tables in Data Stories. Users can select this option to hide table lines and display a borderless table layout when required. ## Question Wall ### New & Improved #### Automatic Regeneration of AI Descriptions After New Question Responses AI-generated descriptions have been enhanced to remain synchronized with the latest stakeholder responses. When a new AI prompt question is added and answered, the system re-evaluates whether all assigned questions are completed. If all responses are available and auto-generation is enabled, the description is automatically regenerated using the latest answers and replaces the previous description. #### AI Description Generation with Existing Description as Context AI-generated descriptions have been enhanced to improve continuity, quality, and contextual relevance. Existing descriptions can now be included as contextual input during AI description generation based on configuration settings. When enabled, the regenerated description uses the existing description along with selected metadata inputs to produce a more refined and consistent result. A new configuration, ai.generatedesc.object.metadata.config, allows administrators to control which metadata elements are included in AI prompts. Supported inputs include object name, hierarchy, associated tags or terms, question and answers, existing description, previous AI output, and additional user prompts. #### Reply to Question Wall Threads from External Notifications Question Wall notifications have been enhanced to support direct replies from external notification channels. Users can now reply directly from supported notifications such as Email, Google Chat, Microsoft Teams, and Slack. Responses are automatically posted to the corresponding Question Wall thread in the application with the correct author and timestamp. **Supported notification events include:** * Question Assigned * New Reply Received * Mentioned in Question Wall Notifications continue to retain their event-specific context. For reply notifications, recent conversation history is also displayed to help users respond with the latest context. Existing notification triggers, audience rules, and permission controls remain unchanged. Only authorized recipients can reply through notifications. #### Question Wall Default Landing Wall for Faster Question Creation The Question Wall module has been enhanced to improve navigation and user engagement. Users are now redirected to a predefined default wall when opening the module, providing immediate access to existing discussions and enabling new questions without additional navigation steps. #### Question Wall Nudge Feature for Faster Assignee Responses The Question Wall module has been enhanced with a **Nudge (Poke)** feature to help question owners follow up with assignees and improve response times. Question owners can now send a reminder notification to current assignees without adding comments or changing the question thread. The **Nudge Assignee** action is available on the Question detail page and is visible only to the question owner. Notifications are sent to assigned users, requesting attention on the question while keeping discussions uncluttered. To prevent excessive notifications, configurable guardrails are applied, including limits on nudge frequency and the number of nudges (pokes) allowed within a defined period. When limits are reached, the action is temporarily disabled until it becomes available again. *** Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ovaledge.com/release8.2/minor-release/release8.1/release-notes/collaboration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.