RabbinatixDocs
Sign inGet started

Work as a team

Automatic tickets and automation

Tickets that open and close themselves when a contract breaks, a test case fails or a service goes down, plus request tickets, access tickets and your own automation rules.

Open Ticket settings in the app

Tickets that open and close themselves

Rabbinatix already knows when something is wrong. Automatic tickets turn those problems into work on the board. When the problem goes away, the ticket closes itself with a comment. When it comes back, the ticket reopens. You never get two tickets for the same problem.

Automatic tickets show an ⚙ auto badge. Untick Show auto tickets on the board to hide them.

The rules

Turn each rule on or off in Settings → Tickets → Automatic tickets.

RuleOpens a ticket whenCloses when
Broken contractsA contract turns BROKENIt is healthy again
Contract warningsA contract has warnings (off by default)The warnings are gone
Unresolved contractsA consumer expects an endpoint the provider has not declared. One ticket per endpointThe provider declares it
Failing test casesThe latest run of a test case failsThe test case passes
Deprecation migrationsA consumer still calls a deprecated endpoint. One ticket per consumerThe consumer stops calling it
Member onboardingSomeone is invitedYou close it. If the invite is revoked, a ticket nobody worked on is removed, and one someone changed or commented on closes as Won't do
Services downA health check says a service is downThe check passes again

For contract rules, Assign to picks the provider or consumer team. For failing test cases, Flows sets how critical a flow must be, and a test case that already has an open ticket someone made for it (such as Create bug ticket on its run) gets no automatic one besides. Tag adds a tag to every ticket the rule opens. Turning a rule off leaves its tickets alone, and Close all closes the open ones.

A broken-contract ticket lists the mismatches and has Open contract. A failing-scenario ticket links the failing run and the exact flow step, and has Re-run test case. See contract statuses and test cases and runs.

NoteIf you close an automatic ticket while the problem is still there, it stays closed until the problem clears and comes back.

Request tickets

Request tickets ask someone to build something and stay linked to what gets built.

  • API request: asks a provider for an endpoint. Create placeholder adds the endpoint to the provider, Implement with logic starts its logic. Moving the ticket through columns sets the endpoint's lifecycle, and deploying the endpoint moves the ticket.
  • Unresolved contract: Accept as API request turns it into an API request and keeps its comments.
  • Flow request: Create flow opens the new-flow dialog filled in. When the flow is verified, the drawer suggests moving the ticket to done.
  • Logic request: Create logic makes the logic. When it compiles and its test cases pass, the drawer suggests moving the ticket to done.

Access and member tickets

  1. Anyone can choose Request access in the account menu, or in the message that appears when their role is not allowed to do something.
  2. The request goes to people who manage members: they get a notification, and Members and teams shows it next to the person. The drawer shows what would change, for example a role from Viewer to Developer.
  3. They click Approve & apply to make the change, or Reject with a reason. The requester is notified either way.

You can't approve your own request. Access requests are visible only to the requester, the person they are about and people who manage members. Inviting someone opens an onboarding ticket for the inviter, with a short checklist. Once they join, it is named after them and stays open until you close it. See members and roles.

Tickets across the app

Systems, flows, flow steps, logic nodes, contracts, requirements, test data and expected results show their open tickets. A system's Tickets tab lists every ticket about its endpoints, contracts and logic. A run result has Create bug ticket, which links the run and the failing step.

Automation rules

Rules follow a when, if, then pattern. Make them in Settings → Tickets → Automation rules.

  1. Give the rule a Name.
  2. Under When, pick a trigger, such as Ticket created, Ticket moved, Overdue, Deadline missed, Linked contract broke or On a schedule.
  3. Under If the ticket matches, type a query in the board's query language, for example type:bug priority:urgent.
  4. Under Then, add actions: Assign, Set a field, Add a tag, Move, Comment, Create a sub-task, Post to chat or Notify.
  5. Use Test on a ticket to see what the rule would do, then click Save rule.

Each rule has a Log of its runs.

Templates and other settings

Templates fill the new-ticket dialog with a title, description, checklist and fields. Set Repeat to make a ticket every day, week or month. A monthly one keeps its day: a template on the 31st makes its ticket on the last day of shorter months and on the 31st again after them. The same settings tab also holds Workflow rules (allowed moves and required fields), Ticket deadlines per priority, Custom fields, and Estimation and archive.