Ticket triage

Lighthouse keeps issues and tickets for teams tracking their work in one place. A Beam agent watches for new tickets, reads the title, body, and labels, and applies your rule to set priority and assign the ticket to the right owner. When a ticket is vague, duplicates an open one, or spans several areas, the agent flags it for a lead instead of guessing. A person makes the call on unclear reports and decides which issues belong on the current milestone this cycle. The agent leaves a short note on each ticket explaining the priority it set so the lead can see the reasoning quickly.

Milestones

Lighthouse groups tickets into milestones so teams can plan a release. A Beam agent reads ticket status across a milestone, applies your rule to flag work that is behind or unassigned, and updates the milestone record with the current picture. When a milestone risks slipping its target date, the agent notifies the project lead with the blocking tickets listed out. People decide whether to move a date, cut scope, or reassign work to keep the release on track. The agent refreshes the milestone summary as tickets close so the team always sees how much work is left before the target.

Ticket comments

Lighthouse threads comments and updates onto each ticket. A Beam agent reads new comments, applies your rule to update ticket state when a comment reports a fix or a blocker, and notifies the assignee of anything that needs a reply. When a comment raises a question the agent cannot answer from the ticket history, it routes the thread to a person. Humans handle the back and forth with reporters and decide when a ticket is genuinely resolved. The agent keeps the assignee informed of every state change so nobody has to reread the whole thread to know where things stand.