Report Group Tools

Automatic detection

You can simply mention @Hana and describe your request. If the intent is clear, she will automatically run the relevant report group tool for you.

Introduction

Report group tools allow users to create message updates in message buckets called report groups. Report groups must be named in lowercase snake_case. Example — daily_tech_standup.

Report groups allow for async team management and team logging. Do not have time for a standup? Use report groups for teamwork updates which can then later be taken into context by Hana to answer your questions about the team’s progress.

Standups or team updates are only one way of using report groups. Technically, they can be utilised for several use cases such as:

• Project progress and updates
• Tracking blockers
• Etc.

Prerequisites

• The report group must already exist and be named in snake_case (e.g., daily_tech_standup).
• You must be in the correct active organization to read/update the group.

Available Tools

Tool	Invocation Keywords	Description	Parameters
REPORT_GROUP_QNA	report	Retrieve messages from a report group between two timestamps.	start_timestamp (string, required) end_timestamp (string, required) group_name (string, required)
CREATE_REPORT_MESSAGE	create update	Add or update a report message in an existing report group.	group_name (string, required) highlighted_message (string, required)

How To Use

1. Invoke the Tool: In your Google Chat, use an invocation keyword like create to add a report message or report to query existing messages in a report group.
2. Specify Your Report Details: Clearly define the content of your report message or question. Include project status, tasks completed, upcoming deadlines, or any other relevant information that needs to be documented and shared with the group.

Example 1

create

create a report for the weekly team meeting. Include updates on project milestones, challenges faced, and next steps.

@Hana create a report for the weekly team meeting. Include updates on project milestones, challenges faced, and next steps

3. Manage and Access Reports: Once your report message is created, it can be accessed and managed through the Hana Dashboard. This allows for easy retrieval and review of past reports, ensuring that all team members are aligned and informed.

Hana, update in daily_tech_standup that I completed payments integration but facing an issue with payment confirmation webhook. I will resolve this today and raise a PR EOD.

@Hana update in daily_tech_standup that I completed payments integration but face an issue with the payment confirmation webhook. I will resolve this today and raise a PR EOD

Hana, what did the team report today in daily_tech_standup? Any blockers?

@Hana what did the team report today in daily_tech_standup? Any blockers?

Example 2

updatereport

@Hana report daily_tech_standup summarize today’s updates

OUTPUT:
Daily Tech Standup Updates:

Done:
@Nav Aggarwal onboarded our organization on Lemon Squeezy payments provider and created a product.
@Santhosh Kumar completed super admin access in the dashboard and fixed a notification hiding bug. Also set up hana-server-uat project secrets and created a new database for UAT. Upgraded and tested the next billing cycle API in PayPal.
@Deep Makadiya completed Bugzilla setup, obtained the API key for IGM environment, set up all 9 services of ondc-sdk locally for IGM and Bugzilla testing, and integrated the /issue API in the liveboxapp.

Committed to Complete:
@Nav Aggarwal plans to work on reviewing pending PRs.
@Vishal Soni will continue working on the onboarding pop-up task and addressing PR comments.

Blocker:
No blockers were reported today.

Additional Comments:
@Nav Aggarwal coordinated with @Vishal Soni on PR mergers.
@Santhosh Kumar provided knowledge transfer and discussed PayPal implementation with @Nav Aggarwal.
@Deep Makadiya is yet to test the integrated /issue API in the liveboxapp.

Please let me know if you need more details on any of these updates.

View and Edit

Report messages and groups can be viewed and altered through Hana Control Dashboard

Troubleshooting

• Group not found: Double‑check the group name (snake_case) and your active organization.
• Missing updates: Ensure you queried the right time range; widen the window if needed.

See also

• Tool Quick Reference — one-line @Hana invocations