Ticket board setup10 Paces, 9 Lives · for Chris, Conan, Yeebles and Ly-Ann · about 5 minutes

Open the board

Our tasks live on one shared board at tasks.dopedevelopers.com. The tickets themselves are stored in a private GitHub repo, so the board needs a key (a GitHub token) to read and save them. You make the key once, paste it in once, and your browser remembers it.

You need: a GitHub account, and the invite Ben sent you to the DopeDevelopersGames organization.

  1. Accept the organization invite

    Open the invite email from GitHub and click Join DopeDevelopersGames. Can't find it? Go to github.com/orgs/DopeDevelopersGames/invitation while signed in.

    Done when you can see DopeDevelopersGames under your GitHub profile's organizations.

  2. Start a new token

    Open GitHub → New fine-grained token. If you'd rather click through: profile picture → Settings → Developer settings (bottom of the left menu) → Personal access tokens → Fine-grained tokens → Generate new token.

  3. Fill in the token

    Token name10 Paces ticket board - yourname
    Resource ownerDopeDevelopersGames Not your own name. This is the step people miss.
    ExpirationCustom → one year from today
    Repository accessOnly select repositories → pick 10PacesTaskBoardTickets (the one ending in Tickets)
    PermissionsClick Add permissions → choose Contents → set to Read and write Don't skip this. With no permissions the board can't see anything.

    Leave everything else as it is.

  4. Generate and copy it

    Click Generate token, then the copy button next to the long code starting with github_pat_. GitHub only shows it once. If you lose it before pasting, just make a new one.

    Treat the token like a password. Don't paste it in chat, screenshots or messages, including to Ben.

  5. Connect the board

    Open tasks.dopedevelopers.com, paste the token into the box, keep Remember on this device ticked, and click Connect.

    Done when you see the tickets and "Connected as @yourname" at the top.

Using the board

Find your work
Set Owner to your name. Tick Ready to start only to hide tickets that are still waiting on someone else.
Update a ticket
Change its status or owner from the dropdowns on the right. It saves straight away; you'll see "Saving…" then "Saved". Every change is recorded in GitHub under your name.
Open a ticket
Click its title. You can edit the title, description, group, tier and what it waits on, then click Save changes. Delete ticket asks you to click twice.
Add a note
Open the ticket, type in the Notes box and click Add note. Use notes for progress, questions and links. They're stamped with your name and the time. To remove one, click Delete on the note, then click again to confirm.
Add a task
Click + New task at the top. It's pre-filled from your current filters. New tickets get IDs like TK-001.
Statuses
To do → In progress when you start → Review when it's ready for Ben to look at → Done.
"Waiting on …"
The ticket needs another ticket finished first. Once those are Done it shows Ready.
Tier colours
T1 reuses existing mechanics · T2 adds a perk or modifier · T3 adds a new mechanic · Reuse uses existing art.
Stretch and later
Hidden by default. Tick Include stretch & later to see them.
Someone else's changes
The board checks for updates every 45 seconds while it's open, or click Refresh.

If something goes wrong

"This token can't see DopeDevelopersGames/10PacesTaskBoardTickets"Open your token at github.com/settings/personal-access-tokens, click it, then Edit. Check the repository is 10PacesTaskBoardTickets and Contents is Read and write. Click Update, then Connect again. If the resource owner is your own name, delete the token and make a new one.
"That token isn't valid or has expired"Make a new token (steps 2–5).
Board says "view only" / can't saveUsually your GitHub account only has read access to the tickets repo. Ask Ben to add you to the Task board team, then reload the page. If that's already done, edit your token and check Contents is Read and write.
Using a new computer or browserPaste the same token again, or make a new one.
Still stuckMessage Ben with the exact red error text from the board (not the token).