Setting up Rules

A rule is a short instruction provided to Noxs AI for one-time or systematic execution, delegated by managers to the system. Rules allow Noxs to be proactive: once set up, Noxs performs routine tasks until the manager cancels the rule or the rule's trigger condition disappears.

‍

1.1. Track the Start of Work and Task Setup

Problem solved: work begins without clear ownership or estimates.

• @Noxs сreate a rule: As soon as [ticket type] is moved to the “In progress” status and does not have an estimate, notify the assignee. If the estimate is not added within [time], then escalate to the project manager. If [ticket type] does not have an assignee, then immediately notify the project manager. Add a link to [ticket type] in notifications.
• @Noxs сreate a rule: As soon as [ticket type] is moved to the [status name] status and does not have an assignee, notify the project manager. Add a link to [ticket type] in the notification.
• @Noxs сreate a rule: If [ticket type] is in the [status name] status for more than [time], notify the project manager. Add a link to [ticket type] in the notification.

video

• @Noxs сreate a rule: If the same assignee has [value] or more tickets in the [status(es)] status at the same time, then write to the assignee about the need to check the task statuses. If the number of tickets does not fall below [value] within [time], then escalate to the project manager. Include a link to the ticket in notifications.
• @Noxs сreate a rule: As soon as [ticket type] is moved to the “In progress” status, check for a description. If the description is missing or less than [minimum number of characters], send a notification to the assignee asking to complete the task. If the description is not completed within [time], escalate to the project manager. Include a link to the ticket in the notification.
• @Noxs сreate a rule: If [ticket type] is moved to the “In progress” status and has linked ticket(s) with a “Blocked by” relationship, notify the assignee of a possible dependency. If the dependency is not resolved within [time], notify the project manager. Include links to all linked tickets.

Video

‍

• @Noxs сreate a rule: If the original estimate exceeds [value] hours, then send a notification to the assignee

 asking for decomposition. If after [amount of time] the original estimate is not [amount] hours or less, escalate to the project manager. Include a link to the ticket in the notification.

‍

1.2. Track Work Progress

Problem solved: stalled tasks and sprint slowdowns, team downtime.

• @Noxs сreate a rule: As soon as [ticket type] is moved to [status name], notify the project manager. Include a link to the ticket in the notification.

Video

‍

• @Noxs сreate a rule: If [ticket type] has a priority of “High” or “Critical” and there is no movement (no status updates, comments, commits) for [time] after moving to “In progress”, immediately notify the project manager. Include a link to the ticket in the notification.
• @Noxs сreate a rule: If [ticket type] is in the status of [status] and has not been updated (no comments, commits, or field changes) for more than [time], notify the assignee to update the status or add comments. If there are no changes within the next [time], escalate to the project manager. Include a link to the ticket in the notification.
• @Noxs сreate a rule: If there is less than [remaining time] left until the end of the sprint and there are tickets in the sprint with the status [status], then remind the assignees. If the ticket has no assignee or there is less than [remaining time], then notify the project manager. Include all links to tickets in one message.
• @Noxs сreate a rule: If more than [value]% of the sprint tasks are in the [status] status for longer than [time], then notify the project manager about the risk of slowing down progress.
• @Noxs сreate a rule: If a ticket is moved to [status] but has not passed [status], then notify the project manager. Include a link to the ticket in the notification.
• @Noxs сreate a rule: If a ticket in an active sprint is locked for more than [time], then notify the project manager. Include a link to the ticket.

Video

‍

• @Noxs сreate a rule: If the number of open bugs is more than [value] for [period], then notify the project manager. Add links to recently added bugs to the notification.

‍

1.3. Track Quality of Completed Work

Problem solved: poor delivery quality and repeated rework.

• @Noxs сreate a rule: If more than [value] bugs are linked/created as subtasks to a single task/user story, notify the project manager. Include a link to the original task/user story and the linked bugs.

Video

‍

• @Noxs сreate a rule: If a [ticket type] was moved from “Done” (or similar) back to “To do” / “In progress” (or similar) more than [value] times in [period], notify the project manager of potential quality issues. Include a link to the ticket in the notification.

‍

1.4. Track Time and Estimates

Problem solved: unrealistic estimates and time misuse.

• @Noxs сreate a rule: If a task with the type [ticket type] in [status] is longer than [time], and the remaining estimate does not decrease, notify the assignee. If the situation has not changed in [additional time], then notify the project manager. Include a link to the ticket in the notification.
• @Noxs сreate a rule: If the original estimate or remained estimate has increased by [value]% after the start of work, then ask the assignee to add a comment with an explanation. At the end of the day, send a list of such tasks to the project manager with links and explanations, if added.
• @Noxs сreate a rule: If time logged exceeds the original estimate by more than [value]% and the task is not closed, notify the project manager. Include a link to the ticket in the notification.

Video

‍

1.5. Manage Worklogs

Problem solved: missing or unhelpful time logging.

• @Noxs сreate a rule: If the worklog contains less than [value] words and logged hours exceed estimated hours, then send a notification to the assignee asking to expand the comment. If the comment is not expanded within [time], then escalate the project to the manager. Include a link to the ticket in the notification.

‍

1.6. Track Sprint Scope

Problem solved: scope creep and uncontrolled changes.

• @Noxs сreate a rule: When a user story or task is added to an active sprint, notify the project manager. Include a link to the ticket in the notification.
• @Noxs сreate a rule: When a user story or task is added to an active sprint, ask the creator to add a comment with the reason. At [time], send a notification to the project manager with all user stories and/or tasks that were added during the day. Include a link to the ticket and a comment with the reason for adding to the sprint (if any) in the notification.
• @Noxs сreate a rule: When a user story or task is removed from an active sprint, notify the project manager. Include a link to the ticket in the notification.
• @Noxs сreate a rule: When more than [value] new tasks and/or user stories are added to the sprint, or if the remaining estimate exceeds [value], notify the project manager. Include links to the task list in the notification.

Video

‍

1.7. Track Overall Scope Changes

Problem solved: duplicate work and shifting priorities.

• @Noxs сreate a rule: If a new ticket is created that is [value]% similar to the name of an existing ticket in any status, then send a notification to the project manager. Attach links to all such tickets.
• @Noxs сreate a rule: If a ticket changes priority more than [value] times in [period], then send a notification to the project manager. Add a link to the ticket in the notification.

‍

By setting up these rules in Noxs, you prevent missed updates, unassigned tasks, scope creep, hidden blockers, and quality issues—while keeping managers informed automatically.

‍

2. Reminding and Escalating roadblocks

2.1. Team Reminders

Problem solved: lack of updates and missing dailies.

• @Noxs сreate a rule that will ask all project participants (mark everyone with @all) to write to the thread updates for today. Send notifications every working day at [time]. And if the update is not given within [time], escalate the PM. 
• @Noxs сreate a rule that will send a notification to the team chat every working day at [time] in [time zone] “Enter the time for yesterday and check the relevance of your task statuses before the day.”

Video

‍

• @Noxs create a rule: If a team member has no logged hours for more than [value] days, then remind the assignee to enter the hours. If the hours are not entered within [time period], then send a notification again to the assignee. If the hours are not entered by [time], then send an escalation to the project manager, combining all project participants who fall under this rule. 

‍

2.2. Monitoring Merge Conflicts through GitLab 

Problem solved: unresolved merge conflicts blocking delivery.

• @Noxs сreate a rule: if there is an unresolved merge conflict within [time interval], send a notification to [specify tech lead]. If after [time interval] the conflict is not resolved, then send a notification to the project manager. In the notifications, add the branch name, the author of the changes, the files with the conflict, a link to the merge request, and the time the conflict occurred.

‍

3. Reporting

3.1. Overall Sprint Report

Problem solved: delivery transparency, up-to-date information on fingertips.

• @Noxs Give me a summary of the Sprint report.

‍

The expected result is a summary report with sections:

1. Problems Identified:
   1. Tickets without estimate
   2. Tickets without description
   3. Tickets that require decomposition
   4. Tickets added/removed from sprint
   5. Tickets that exceeded estimation 
   6. Blockers or Critical tickets
   7. Tickets that were blockers

2. Strategy Analysis
   1. Total time spent:
   2. Time distribution per activity
   3. Logged time vs. Original estimate

3. Tactics Analysis
   1. Tickets that reached QA or Done
   2. Bug statistics
   3. Reopened Tickets
   4. Estimation accuracy

3.2. Area Focused Report

Problem solved: delivery transparency, up-to-date information on fingertips.

• @Noxs show all tickets in “To Do” (or similar) status in active sprint with links.
• @Noxs show all tickets in “To Do” (or similar) status in active sprint with links.
• @Noxs Show the list of tickets where logged hours exceeds estimated hours by 40% and more in the current sprint. Group them by the assignee.

Video

• @Noxs Give a list of bugs with critical priority created in the project.

‍

4. Performing SMART Search Across Scattered Sources

‍

Problem solved: significantly reduce time on search of project information, keep knowledge up to date.

‍SMART Search lets you ask natural questions in chat, and the system will look through Jira, Google Docs, Confluence, and GitLab code to give you clear answers.

• @Noxs, how does resume search work?  
• @Noxs, what’s the overview of developer performance evaluation?  
• @Noxs, in which service and file does sprint report preparation take place?  

Video

For better results in SMART search, follow the rules: (i) Be specific: mention the feature, service, or file you need; (ii) Use natural language — no special syntax required, (iii) If multiple matches exist, the bot will show you the most relevant ones.

‍

5. Analysing Team Efficiency

Problem solved: evaluate individual performance of a developer based on the quality of their task estimates, task complexity, merge requests, and expertise.

Reports cover up to 3 months, only one project or all projects, not several at once.

• @Noxs, evaluate @username in current sprint (or project name).

The expected result is a summary report with sections:

1. Estimation Accuracy – planned vs. actual task time.
2. Task Complexity – how complex tasks are handled.
3. Bugs – bug count linked to tasks.
4. Fixes & Inaccuracies – repeated issues, duplicates, status rollbacks.
5. Review Time – average speed of code reviews.
6. Expertise – domains/skills (future feature).