Belltower 1.5.0-rc.4

• Teams, off by default. The team features below (assignees, Mine and Unassigned, watching, @mentions, the bell,
  personal notifications and names in the history) are behind Settings → General → Teams. It's off until an
  admin turns it on (installs that already have several people keep it on), so a solo install looks as it did
  before. Turning it off hides them and deletes nothing; turning it back on brings everything back. See
  docs/USING.md.
  • New tickets from the submit page still ring the bell for admins while Teams is off (the bell shows while the
    submit page is on). With Teams on, they're an event of their own under Account → Notifications, in the app
    for admins by default.
• People. Belltower now has accounts, each one an admin or a member.
  • Admins run the install: people, settings, notification channels, the submit page, backups and restore.
  • Members do all the board work, and manage their own profile, password and API tokens.
  • Settings → People adds someone with a temporary password, changes roles and display names, and deactivates or
    re-enables people. The owner is always an admin.
  • Account, in the ☰ menu, holds your profile, password, API tokens, single sign-on and notification choices.
• Who did what. Every history entry and work-log note shows who made it, including "via API token" and the submit
  page.
  • Only the note's author or an admin can edit or retract a note.
  • Retracting and restoring a note are recorded too.
• Assignees. A card can have one assignee. Pick them on the card, see their initials on the tile, and filter the
  board by assignee.
  • Mine lists your open cards.
  • Unassigned lists every open card nobody has taken, most urgent first, with Take it. If two people grab the
    same card at once, the second is told who got it.
  • On phones the top bar shows icons only, and Calendar and Recurring moved into the ☰ menu.
• Watching, @mentions and the bell.
  • Watch a card to hear about new notes, moves and changes of assignee. You watch a card automatically when you
    create it, are assigned it, are mentioned on it or write a note on it.
  • Type @ in a note to mention someone.
  • The bell in the top bar lists your notifications. It can play a sound on each device (Settings → Appearance).
• Personal notifications. Account → Notifications chooses, for each kind of event, the bell, a Discord ping in
  the install's channel, or your own ntfy topic. See
  docs/NOTIFICATIONS.md.
• Tag-restricted accounts. In Settings → People, an admin can restrict a member to certain tags. They then see
  only tickets that carry one of those tags, everywhere: board, search, calendar, history, the bell, their own
  notifications and their API tokens. Untagged tickets are hidden from them, and with no tags left they see nothing.
  See docs/USING.md.
  • Cards they create get their tags, and they can't manage tags, columns, board-wide actions or recurring templates.
  • A ticket can't be assigned to someone who can't see it. Retagging a ticket, or narrowing someone's tags,
    unassigns them from tickets they can no longer see, and the history says so.
  • Admins and the owner can't be restricted. It works whether Teams is on or off.
• Request types label their tickets. Each request type on the submit page has a list of labels that go on every
  ticket filed with it, so tickets can land straight with the right tag (and the people restricted to it).
  Submitters no longer pick tags. See docs/SUBMIT-PAGE.md.
• The board keeps itself up to date. While the tab is visible, the board, lists, calendar and the open card
  refresh every 15 seconds, and a new ticket now lands on the board together with the bell's chime. These refreshes
  don't keep an idle tab signed in. If someone changes a card's title while you're editing it, you're told before
  your save replaces it.
• Single sign-on (optional). Sign in through Authentik, Authelia or another OpenID Connect provider. See
  docs/SSO.md.
  • With single sign-on on, the login page shows the sign-on button and keeps the password form behind a
    Sign in with a password link. Settings → Single sign-on can show the form again, or turn password sign-in
    off for everyone but the owner, who can still use it at /login?password. APP_PASSWORD still resets the owner.
  • With a required group set, Belltower also asks for the groups scope when the provider offers one (VoidAuth and
    Pocket ID send groups only then), and the log says why someone failed the group check.
• API tokens belong to a person. Members see their own under Account, and admins see everyone's under
  Settings → Automation. A token stops working while its owner is deactivated. The automation API itself hasn't
  changed.
• Upgrading. There's nothing to do, and nobody is signed out.
  • Teams starts off, so the board looks as it did in 1.4 until an admin turns it on (installs that already have
    several people keep it on).
  • Your password becomes the owner account admin. The name tower-tracker that password managers saved still
    works.
  • Signed-in devices and API tokens move to the owner.
  • APP_PASSWORD now sets the owner's password only, and "set it and restart" still gets you back in.
  • Backups now include people, but never their passwords. Restoring keeps the accounts of the install you restore
    into, and backups from every earlier version still restore.
  • Each request type keeps its "Always add the label" as its one label. The lists of tags submitters could pick
    are dropped; add any you still want to the type's labels.
  • Nobody is restricted to tags until an admin sets it.
  • If you already use single sign-on, the password form moves behind a link on the login page. Nothing else
    changes until an admin turns password sign-in off.
  • The database moves to layout 11. Going back to 1.4 means putting back the copy saved before the upgrade, and any
    accounts created since are lost (see docs/UPGRADING.md).
  • From a 1.5.0 release candidate (rc.1 to rc.3): the same notes apply; the database moves from layout 9 to 11.

Belltower 1.4.0

• Checklist marks. Clicking a checklist item now cycles through three marks, then back to empty: ✓ done, ✗ failed
  (or "no" to a yes/no question), and ~ couldn't verify or still in progress.
  • ✓ and ✗ both count toward progress. The card's progress bar shows ✓ in green and ✗ in red.
  • On the board, a ticket's checklist badge turns red when any item failed and yellow when any couldn't be verified,
    so a failure doesn't hide behind "5/5".
  • Clicking through several marks quickly records only the one you stop on in the history.
• Upgrading. Items checked before 1.4 show as ✓, the automation API hasn't changed, and backups from every
  earlier version restore. The database moves to layout 8, so going back to 1.3 means putting back the copy saved
  before the upgrade (see docs/UPGRADING.md).

Belltower 1.3.0

• Status links for people who file tickets. After sending a ticket from the submit page, people get a link they
  can bookmark. It opens a page, no sign-in needed, with the ticket's title and number, when it was sent and last
  moved, and whether it's received, being worked on, waiting on something or done. Once it's done, the page also
  shows the resolution reason. Descriptions, notes and work logs stay private.
  • Status link on any ticket copies its link, so you can also send one to someone who told you in person.
  • Settings → Submit page → Reset status links cuts off every link handed out so far. See
    docs/SUBMIT-PAGE.md.
• Seen this before? An open ticket lists up to five finished tickets that look like it, archived ones included.
  Each shows the resolution reason and the start of the note, so last time's fix is right there. Link links one
  as related. Add ticket shows up to three matches under the title once it has two words.
• ntfy, Gotify and webhooks. Notifications can now go to ntfy, Gotify or any webhook, as well as Discord.
  • Each channel picks its own events. For example, everything can go to Discord and only urgent tickets to your
    phone.
  • Webhooks get a versioned JSON body that can be signed with a secret. See
    docs/NOTIFICATIONS.md.
  • Discord sends the same messages as before.
• Ticket counts on your dashboard. GET /api/v1/summary gives counts for Homepage, Home Assistant and similar
  dashboards: open tickets by state, urgent, overdue, finished today and in the last 7 days, and more.
  • It uses a new kind of API token that can only read those counts.
  • Settings → Automation shows a ready-to-paste Homepage and Home Assistant setup for it. See
    docs/AUTOMATION.md.
• Fixes:
  • A daily summary that fails to send now waits 30 minutes before trying again. Before, it retried every minute for
    the rest of the day.
  • Deleting the column the submit page files into could let a new column quietly receive submissions. The setting
    is now cleared along with the column.
• Upgrading. Existing API tokens keep doing everything they did, and backups from every earlier version restore.
  The database moves to layout 7, so going back to 1.2 means putting back the copy saved before the upgrade (see
  docs/UPGRADING.md).

Belltower 1.2.3

The app itself hasn't changed. This release tidies up around it.

• Try it without installing. The live demo runs the real app in
  your browser with a sample board, and your changes stay in that browser. View as Submitter shows the submit page.
• Screenshots in the README, in light and dark to match your GitHub theme.
• Shorter docs. The upgrade notes for betas and for coming from Tower Tracker are gone, since releases before
  1.2.1 are no longer published. The original design proposal (docs/DESIGN.md) is retired; the reasons behind the
  stack now live in docs/DEVELOPMENT.md. The README no longer calls Belltower early
  development.
• Release workflow. The old beta channel is gone. Releases are latest (and 1, 1.2, 1.2.3) or rc.

Belltower 1.2.2

What's Changed

• v1.2.2: use the real icon in the top bar and sign-in page by @bernie-sandler in #18

Full Changelog: v1.2.1...v1.2.2

Belltower 1.2.1

The app itself hasn't changed. This release makes the files that ship with a release match the new image address.

• The right image out of the box. docker-compose.yml now uses ghcr.io/bernie-sandler/belltower. The copy in the
  1.2.0 release still named the old address.
• Older versions are retired. Images now go back to 1.2.0, and ghcr.io/bernie-sandler/tower-tracker and the
  earlier releases are going away. If TT_VERSION is set to rc, beta or anything before 1.2.0, change it to
  latest. Your data is safe either way: 1.2.1 reads every older database and backup.

Full Changelog: https://github.com/bernie-sandler/Belltower/commits/v1.2.1