Issue.coffeeSuite.coffee
Set-up and organisation

Set up Issue.coffee

Define regional settings, deadlines, verification, notifications and safe reporting channels.

1 min readUpdated Aug 23, 2026

Prepare the regional context, lifecycle rules, notifications and safe reporting channels before daily use.

Before you start

  • Agree the internal issue workflow and closure policy.
  • Confirm timezone, language and due-soon threshold.
Issue settings with regional context, workflow, notifications and public reporting options.
Settings define common lifecycle rules and which controlled channels are active.

Review the operational workflow

Confirm timezone, language, due-soon threshold and whether a different person must verify closure. Choose the team notifications that support real follow-up.

Enable channels deliberately

Public reporting, email verification, API and webhooks are independent options. Publish or activate each one only after its categories, locations, credentials and recipients are ready.

Keep the service boundary clear

Issue tracks internal operational problems and corrective work. Customer support conversations belong to Ticket.coffee; account, plan and general members remain in Suite.coffee.

Step by step

  1. Open Settings.
  2. Confirm country, language, timezone and first weekday.
  3. Set independent verification and due-soon hours.
  4. Choose internal notifications.
  5. Enable public, API or webhook channels only after testing them.

Final check

  • Dates use the intended timezone.
  • Closure rules match the team policy.
  • Only prepared channels are active.
Tip: Issue tracks internal operational problems; customer support belongs to Ticket.coffee.