What was added most recently.

/api/admin/recurring/run?token=… and /api/admin/notifications/run-due-checks?token=… are meant for an external cron and check their token themselves. The middleware did not know about the token in the address and sent the call to /login — so scheduled recurrences were never triggered by cron at all. Both paths are now exempt from the middleware; the routes stay switched off without ADMIN_CRON_TOKEN and answer with 403 on a wrong token.

The “open workspace” button in the company list and the company detail view led back to your own home page for workspaces you are not a member of. It now only appears for workspaces you belong to; otherwise it says “access via support code” with the route to support access.

The mail log (recipient, subject and time per message) grew without limit; it was only cleared when an admin clicked “delete old entries”. A retention period of 90 days now applies (configurable via MAIL_LOG_RETENTION_DAYS, minimum 7): entries older than that disappear by themselves — once a day when mail is sent, and with every tick of the cron call. The admin page says so. That lets the privacy policy name a real period.

/.well-known/assetlinks.json carried a placeholder, which is why links to tasks opened the browser rather than the app on Android. The SHA-256 of the upload key is now in it. If the app is distributed through Google Play, the Play signing key has to go into the array as well. iOS stays open until there is an Apple Team ID.

POST /api/workspaces recorded the creator as an administrator rather than the owner. Nobody could delete or hand over workspaces like that. The creator now becomes the owner; for existing ones there is npm run repair:owners (with --dry-run to look first): the oldest administrator member, failing that the oldest member, becomes the owner.

The desktop app places its three window buttons over the page in the top right. The workspace header already got out of the way; the personal workspace, side sheets from the right and toasts did not — the user icon, the close cross and messages were covered there. Everything now gets out of the way, and no new desktop build is needed for it.

The estimation scale sat under General between name, colour and counters — a foreign body. It governs how tasks are sized and therefore belongs with “how tasks run”: next to the statuses under workflows.

The icon picker had 29 symbols. There are now around 160, sorted by theme (work, technology, communication, places, finance, nature, people, animals), with a search field and a scrollable grid. Saved icons stay valid.

In the company detail view (members tab) and in the user detail view (memberships), the role is now a select field rather than a read-only display: owner, administrator, member, viewer. There is a confirmation before saving, the last owner cannot be demoted, and every change is recorded in the audit log with its before and after.

Anyone needing help previously had to hand support their credentials or invite them permanently. An owner or administrator now generates a code (“SUP-XXXX-XXXX”) under Settings → General → support access and gives it to support. Support redeems it in the admin area and is then a member with administrator rights for 1, 7 or 30 days — not owner, no billing. The access ends by itself, can be ended at any time, appears in the member list for as long as it lasts (with its expiry date), and a notice above the page shows all members that it is active. Every redemption and every ending is recorded in the admin audit log.

The project page now answers “how is this project doing?” first: below the header sits a status line with progress (open / done), the state from the latest update (“on track”, “at risk”, “delayed” — or “no update”), the target date, the next milestone and open blockers. Below that, tabs: Overview (latest update, next milestone, open blockers, who is working on what, recently moved), Tasks (the list as before), Milestones (every stage with a checkbox, status directly selectable, target date in red once overdue, a bar for the linked tasks), Updates (a timeline with a traffic-light dot, who and when, the text) and Documents & links. Previously milestones, updates, documents and links stacked up in a narrow side column next to the task list, and below it on a phone — you scrolled and searched. The tab is part of the address (?tab=updates), so links to it work.

As soon as a workspace held more than 100 tasks, whole status groups went missing from “All tasks” — “In review” and “Inbox” were gone, and the top right said “100” as if that were all of them. The cause was a blanket limit of 100 rows after sorting; the oldest quietly dropped out, even when they were open. Open tasks are now always loaded in full. Completed and cancelled ones stay capped at the 100 most recently closed — older ones are found through the archive and search.

In light mode, the top left of the collapsed navigation showed the white icon tile — on a light background it looks like an empty placeholder. Both themes now show the blue tile there, the same one as the favicon.

The cycle dialog used to open with three empty fields and not a word about what a cycle is. The explanation now sits at the top of the dialog, the name is pre-filled with “Sprint N” (N counts on from the team's highest existing cycle), the start is today and the end is two weeks out. A quick choice of “1 week · 2 weeks · 4 weeks” sets the end, and moving the start takes the end along — the duration stays. Anyone who simply confirms ends up with a usable cycle.

Selecting several tasks in the list and then setting, say, the status lost the selection — everything had to be clicked again for the next action. The selection now stays; only archiving clears it, because those rows are no longer in the list afterwards.

Next to the title of projects, initiatives, cycles, releases, views, day summary, customers, vault and files there is now a small “?” — hovering it explains in two sentences what the section is for and how to use it. Instead of a dash, a new project shows concrete tips: what milestones are and what a weekly update looks like. Deliberately restrained: one symbol, no prose, nothing that costs space.

“New view” creates the view immediately — as “New view”, “New view 2”, … — and opens it straight away as a list. No more dialog asking for name, description and layout before you have seen anything at all. Inside the view everything then happens in place: change the name right in the header (click, type, Enter), set filters in the filter panel, choose layout and grouping — and as soon as something differs from the saved view, “Save view” appears in the header. No more detour through the edit menu in the list.

The team can be changed from the task detail view. The task takes the next number in the target team (DEV-151, for example), the status moves to the target team's status of the same name (failing that, the same category; failing that, the inbox), and a cycle is dropped, because cycles belong to a team. Comments, attachments, labels, project, history and subscriptions all stay. The detail page jumps to the new identifier, and the history reads “moved the task from “TASK-3” to “DEV-151””.

An “@Anna” in a comment now appears as a chip; when it is your own name, the chip is stronger — the line you are reading the comment for catches your eye immediately. Unknown @ words stay plain text.

A title that was too long produced “Error” with no explanation. The message now says “Title: 300 characters at most”, and the title fields in the create dialog and the detail view no longer accept more in the first place. This applies to every input error from the API: field, reason, limit.

After DEV-126 (the checkbox in the recurrence editor) two places still used the native element, which renders as a dark block: the selection column in the admin workspace table and the event picker on the integrations. Both now use the shared checkbox.

The last two differences from the workspace board have been evened out: the column title uses the same font weight, and the card list no longer has extra space above it. “1:1” now means 1:1.

The filter panel has two tabs. Simple is the familiar selection per dimension. Advanced is a rule builder: one field per row (status, priority, assignee, project, team, label, due date, SLA, SLA status, blocked, stalled), “is” or “is not”, and the values — with the one decision above it of whether all rules must hold (AND) or one is enough (OR). That makes things possible that were not before: hiding two teams, “open OR urgent”, “project is not: no project”. Both tabs apply together; the chip bar above the list spells out every rule and lets you remove them one at a time.

Board cards in the workspaces now behave like the cards in the personal workspace — in both densities, compact and detailed. Sub-tasks sit as a checklist right on the card: a tick completes the sub-task (and reopens it), hovering reveals “add sub-task”, and Enter creates one and leaves the row open for the next. A click anywhere on the card expands it (previously only the title), Tab reaches it, Enter opens it and Escape closes it. The gap between title and meta line is the same as over there. What the workspace card additionally shows — assignee, identifier, priority, blockers, time — stays discreet at the same small size.

The left-hand navigation has a button in its top right that collapses it into a narrow icon bar — animated, not switched. Everything stays reachable while collapsed: workspace, “new task”, the main navigation as icons with counters, the teams as avatars, settings and your own account. Hovering an icon shows the name, counter and keyboard shortcut beside it. The state is remembered — per browser, across reloads and page changes, without the bar first building up wide on load and then snapping shut.

Label chips, team keys, project dots and the workspace colour showed exactly the colour picked in light mode when in dark mode. On white, a medium-saturated red is an ordinary chip — on the dark surface the same colour glowed like a warning signal, and since the surfaces have been calmer it stood out all the more.

Every label change in a task's history read “added the label “—”” — the name had been missing for as long as the history has existed. And clicking repeatedly in the label picker produced the same sentence nine times over, even though nothing had changed. It now reads “added the label “Bug””, for old entries too, and only when the label really was added or actually removed. A label that has since been deleted is named as such rather than shown as a dash.

The due date (“31 Aug”) on the personal workspace cards was as large as the other meta items and sat two pixels below the title. As a red filled pill it read like a second title. The chip is now one step smaller and the meta line of the collapsed card moves noticeably away from the title — the card reads in the right order again: title, then side note.

The “mark all as read” button in the inbox used to tick off everything — across all workspaces. The list below it showed only one, and the bell popover even said “this workspace only” next to it. Tidying up inside one client project therefore also wiped out the unread items of every other workspace.

When an attachment was deleted the row disappeared at once, but the number beside it — “Attachments (3)” and the counter on the “Overview” tab — stayed put until the server caught up. For a moment it looked as though the deletion had not gone through. The heading now counts down in the same instant, and the same goes for uploading and pasting from the clipboard.

Under Settings → Appearance the labels “icon” and “colour” sat right against the box below them, with no room in between. They now sit cleanly above it.

In the recurrence picker, “carry over sub-tasks” was still a raw browser checkbox among otherwise designed controls. It now uses the same checkbox as the rest of the interface.

As soon as a filter takes effect, a bar appears directly above the list: “4 of 137 tasks” and, beside it, a chip for each active criterion in plain words — Status: open, Team: DBD, Search: “hero”. Every chip has an × that removes exactly that one criterion; a second × at the end of the row clears everything at once.

A widget can offer its own report types and route them to a particular team depending on the choice. None of that arrived when converting by hand: the inbox always proposed the widget's default team, and because that choice is sent along when the task is created, it overrode the routing. Anyone picking “billing problem” in the widget still had their report land in the default team. Only automatic conversion worked correctly.

The dialog for creating a task was crowded and inconsistent. The team field clung to the heading as a box of its own, the chips for priority, assignee, labels and template had three different heights and borders, and at the bottom hung a grey block with a bare checkbox for recurrence. In the footer, the keyboard hint, a switch and two buttons crowded into one row and all wrapped in narrow windows.

In dark mode, wide lightened bands lay across the lists — the group headers (“In progress 4”, “In review 8”). The same headers step back in light mode, where they are barely more than a line of text with a hairline beneath. On top of that came a strong navy tone across all surfaces. Together, the two made the dark variant look busier and cheaper than the light one.

Under Settings → My profile there is now “delete account permanently” at the very bottom. Until now this only worked by messaging us. Google Play requires a route for the app that people can take themselves — including a public page a reviewer can open without an account. Both are in place.

Switching to the board in “All tasks”, “My tasks” or a saved view did show the board — but the switcher above it stayed blank, as if nothing had been clicked. Both tabs looked equally uninvolved. The active tab is recognisable as such again.

Two identically built buttons sat side by side in the filter row — and ended differently: “sort” with a blue arrow, “group” with a grey chevron. Two colours with two meanings in the same place; it read like a mistake, but it was intentional.

Replying to a widget report in the inbox produced the success message — but the reply did not show up in the card's history. Only reloading the page revealed it. It looked as though nothing had gone out; it had been sent long before.

Until now the live issue widget offered exactly three types — bug, idea, feedback — and everything landed in the same team. Anyone handling billing questions differently from usability problems had to sort them by hand afterwards.

On the board, the detailed view was missing things the compact one had long had — and both were missing icons the personal board already shows. The reason: they were two separate card components, and every alignment had to be made twice.

In around 25 places the edit and delete icons were invisible until the mouse hovered over them. Their space stayed occupied all the same — a dead gap yawned at the end of the row, the content looked shifted, and anyone who did not already know about the actions never found them.

Several settings pages showed everything at once, or things that belong elsewhere. They have been tidied up — and where a page left a question open, it now answers it.

The configuration check said “missing: 4” at the top while the button below it said “nothing to do — the .env already knows every key from the example file”. Both were true on their own but contradicted each other: the count included keys that the example file merely describes as a comment. There is nothing to add for those — they are an explanation, not a shortcoming. Anyone taking the number seriously went looking for a fault that did not exist.

Anyone capturing mail from the same customer every day has had to pick the same destination anew each time. From now on you can record which sender belongs where: “everything from @ryvelia.com into the Ryvelia project.” The destination is then already filled in when capturing.

Ten tasks out of one meeting used to mean doing the same thing ten times: open the dialog, choose the team, choose the priority, choose the assignee, type the title, submit. With the new create another switch in the dialog footer, the window stays open after creating and keeps everything that describes the frame — team, priority, assignee, labels, template, recurrence. Only what belongs to exactly one task is cleared: title, description, attachments. The cursor is back in the title field immediately.

Favourites were missing after an import and nobody could say why. The star is visible in the source program, so it looked like a fault in the import — when in fact most of those interfaces do not hand it over at all. Google Tasks had started saying so recently; the other four stayed silent.

Anyone standing in a team's backlog who presses C wants a task for that team. The modal nevertheless said “no team” — the task landed in the catch-all team, and whoever noticed only later had to move it by hand.

After a deploy the question was always the same: what is actually in it? The answer only existed in a markdown file in the project — on the server where the changes run, there was nowhere to look it up.

The Firefox download was a dead end. On its normal channel, Firefox only accepts add-ons signed by Mozilla — the switch that gets around this in Thunderbird is simply ignored there. Anyone who downloaded the file got “could not be installed because it could not be verified” and that was that.

Anyone who had narrowed a list down to a project or an assignee found everything back again on the next page view. The filter was pure session state — every reload, every jump to the board and back threw it away.

Tasks created in Gmail out of an email carry a route back to that exact message at Google. That was lost on import — the task arrived, the context stayed behind, and you went hunting for the mail in your inbox again.

A board is a board — yet the personal workspace and the team workspaces felt different. The cards were thicker, the corners rounder, the columns different heights, and the hint about scrolling sideways was missing entirely.

Until now only a team workspace could be marked as the default. Anyone working mostly alone, with their teams only on the side, could not make their personal workspace their home — even though that is where their work sits. Now they can: right-click “workspace” in the workspace switcher → set as default. The star then shows what applies. The same choice sits under Settings → default workspace.

Anyone who wanted to turn emails into tasks with a click and uses Firefox was out of luck: the Gmail extension existed only as a ZIP for Chrome, Edge and Brave. The same extension is now also available as a Firefox package — with the same button in Gmail, the same destinations and the same jump back to the mail.

Anyone fetching their tasks out of Google Tasks could select exactly one list. With nine lists that meant nine runs, each from the start — connect, select, preview, import. And where the tasks went was not up for choice: every list inevitably became a team of its own. Nine Google lists turned into nine teams, which was almost never what was meant.

Next to the Windows download sat a button for macOS. Clicking it landed you on an error page: the Mac build is not produced at all at the moment, because an Apple developer account is missing. The button is now hidden — better no offer than one that cannot be honoured.

Anyone wanting to connect their Google account did not arrive in IssuePilot after consenting at Google, but on a bare “403 Forbidden” page from the server. The account was not connected, and a second attempt ended the same way — without anything anywhere saying what the cause was.

In the team dialog under Settings → Teams you had to come up with the key yourself before it was even clear what it stood for — a required field right next to the name. The onboarding wizard did make a suggestion, but it was wrong in three cases: umlauts dropped out, multi-part names produced only the first three letters of the first word, and once you had touched the field you never got a suggestion again — not even after clearing it.

Anyone registering and saying they work alone still had to name a team first, assign a key and pick a colour — for something they did not want at all. After that they were walked through projects, cycles, customers and “invite your team”, while their actual workspace got a single row of tiles.

Tasks from Google Tasks, Linear, Asana, Trello or Jira could previously only be pulled into a team workspace. Anyone using the personal workspace — or not belonging to a team at all — could not reach their own Google tasks and had to retype them.

Anyone dismissing a notification on their phone — in the app or straight from the “read” button on the push message — still saw the old number on their computer: in the inbox, on the bell and as the badge on the desktop app's icon. Only reloading the page cleared it up.

Whether a server had all the necessary settings could previously only be answered over SSH by comparing text — and usually only came to light when a feature quietly did nothing. The new System admin → configuration area puts the server's .env side by side with the bundled .env.example and says at a glance what is missing, what is empty and what is there on top. The sidebar shows the number of anomalies as a red counter, so you do not have to visit the page to find out.

The mail extensions could not connect to the server at all — both Thunderbird and Gmail simply said “connection failed”, no matter how correctly the address and key were entered. The fault was on the server, not in the input. That is fixed.

Until now you had to get at the mail extension files through the project folder and type the server address in by hand. All three now sit under Settings → Integrations ready to download — with a version number beside them. And the address is already filled in: anyone downloading the package from their own IssuePilot only has to paste in the access key.

Turning an email into a task previously only worked in Gmail and Thunderbird — Outlook, the program most business customers use, was left out. There is now an Outlook add-in for desktop, web, Mac and mobile. And the mail stays attached to the task: the task view has a card of its own, “email”, with the sender and a button that reopens the message. Until now that link disappeared into the middle of the description text.

A team could previously only be deactivated. It vanished from the lists but stayed in the database forever — anyone who mistyped when creating one, or dropped a structure, never got rid of the team. There is now real deletion, and by the only route that is safe: tasks move to another team first, and only the empty team is deleted. Both happen in one step — so it cannot happen that the tasks have moved and the team is still standing.

Anyone who had collected their tasks in Google Tasks so far had to retype them to get started with IssuePilot. Google Tasks now stands as a fifth import source alongside Linear, Asana, Trello and Jira — with the same guided flow: connect, choose a list, check the preview, import. Unlike the other sources there is no token to paste: Google does not issue API keys for tasks, so you sign in with Google once directly. IssuePilot only ever receives read access — nothing in Google Tasks is changed or deleted.

A team used to consist of five lists. Anyone wanting to know how the team was doing had to open four tabs and add things up in their head — and who was in the team appeared only in the edit dialog under settings. Every team now has a home page that answers the questions you ask on walking in: what is coming up? what is stuck? who is carrying how much? are we getting faster or slower? Every answer is clickable and leads into the matching, already filtered list.

Until now every task had to be assigned to a team — and because the field was pre-filled, in case of doubt it landed with the first team in alphabetical order without anyone having decided that. “No team” now sits at the very top and is the default. A team is something you choose deliberately.

The “assigned” tile on the dashboard counted every task that had ever landed with you — completed, rejected and archived included. It could therefore only grow and said nothing about actual work any more. It now shows open tasks. On projects, cycles, releases and teams the number now reads “3 / 12”: three still open, twelve in total.

Clicking, dragging and switching felt as though the interface simply jumped — every action was instantly finished, but nothing confirmed it. Every button now dips briefly when pressed, dragged cards visibly lift off the surface, the target column glows softly and a change of view slides in rather than switching. None of it costs waiting time: every movement sits between 120 and 240 milliseconds.

There used to be only “select all visible” — anyone wanting to move every task out of “in progress” had to click each row individually, or select everything and deselect the rest. Every group header in the list now has a checkbox of its own: one click takes the whole group, a second releases it again.

The admin overview was a wall of numbers without context: 24 tiles, all equally important, none of them saying whether any of it was good or bad. At the very top it now says what someone should look at — every line with a link straight there. Below that, charts show where the platform is heading, and every metric names its change against the period before.

In the admin lists, a long email address or a long company name pushed the table past the edge — status and actions could only be reached by scrolling sideways. Role chips wrapped and ran outside their coloured background as they did so.

Users, companies, subscriptions and widget reports quietly stopped at 100 entries. Anyone with more could not reach the rest — and the interface did not say anything was missing. The total, the page number and a selectable number of rows now sit there.

On the pinboard the small buttons in the top right (colour, rename, bin) could no longer be hit — something was lying over them.

Nothing at all could be done in the archive on a phone — neither restoring nor deleting, and you could not even see which task it was about. That is fixed. On top of that, tasks can now be selected and restored or permanently deleted together.

The settings used to list every area to every member — including members, billing, integrations and the complete data export. You were allowed to click everywhere and only failed when saving. Every role now only sees what it is responsible for.

Alongside light, dark and system there is now “schedule”: you set from when until when it should be dark — dark by itself in the evening, light again by itself in the morning, without switching over every time.

The widget settings now name who is notified about a new report. And former colleagues no longer receive reports.

The integrations list now shows the real brand marks instead of the same speech bubble four times over. As a side effect it emerged that Microsoft Teams had stopped delivering anything at all with newly created webhooks — that is fixed.

A duplicated note disappeared behind its original — it looked as though nothing had happened. And anyone duplicating from inside a folder could not find the copy there at all.

Connections previously only existed between two notes. A line can now also end at a folder or start from one — note to folder, folder to note and folder to folder.

When creating or editing a note on the pinboard, the save button stuck out past the right-hand edge of the card.

Notes, files and timeline now have their own addresses — /my-space/notes, /my-space/files, /my-space/timeline. Until now all four sections sat behind a single page: anyone who had their notes open and passed the link on or reloaded ended up back at the tasks, and the back button jumped out of the workspace instead of one section back.

The workspace switcher showed 4 unread notifications while the inbox said 6. Every display of that same number — switcher, sidebar, bell and the desktop app's icon — now refers to the same figure delivered by the server.

The right-click menu on notes opened, but no item reacted to a click. Merging two notes into a folder also happened without any visible moment, and anyone opening a folder landed on what looked like an empty surface.

You can now create folders on the notes pinboard — by dragging one note onto another, like on a phone's home screen. A click opens the folder as its own, again endless surface; new notes are created there the same way, and the same drag gesture creates subfolders. A bar at the top shows where you are, and every folder card carries a bubble with the number of notes inside. Inside a folder, search now only covers that folder and everything below it.

Longer notes ended abruptly at 160 pixels on the pinboard, often mid-word — that looked like a defect rather than “there's more to read”. The cards now show almost twice as much, and when there really is more, the text fades out softly towards the bottom. Notes also gained a right-click menu.

The switcher now shows next to every workspace how many unread notifications are waiting there. Until now you only saw that after you had switched over.

Anyone who ticked off a notification on their phone saw the counter in the navigation on their computer stay exactly where it was — and the other way round. Only a reload brought the two to the same state. The counter now follows immediately on every signed-in device, including the desktop app's badge.

Anyone with the app open while a deployment was running got “Application error: a client-side exception has occurred” — for one to three minutes, on every deployment. The build now writes into a second directory and is only swapped in at the end; the window shrinks from minutes to milliseconds. Open tabs survive the switch unharmed as well, because the files from the previous build are carried over.

Anyone who signed up with a name without Latin letters (Cyrillic, Greek, Chinese) got a workspace with no URL slug at all — afterwards it could not be reached under any address, and every link to it led nowhere. Sign-up now assigns a usable slug in every case, falling back to the front part of the email address. On top of that, the slugs the app uses itself are blocked (“admin”, “api”, “login” …) — until now you could create a workspace that you were never able to open again.

Notes in your personal space can now sit on a free pinboard instead of only in the column grid. Cards can be dropped anywhere, moved, coloured and joined with lines — enough mind map to see how things relate, without forcing a root and branches. The surface grows in every direction, dragging pans the view, Ctrl + scroll wheel zooms. If you would rather see everything at once, one click switches back to the familiar column view; the choice is remembered per device.

Notifications can now be controlled individually per event type and channel (in-app, email, push). Emails now also go out for personal tasks (assignment, due reminder) and — opt-in — for status changes, widget reports and portal messages. If you want fewer emails, pick the daily summary instead of individual ones. Owners and administrators use the new notification policy to set, per workspace, which settings are mandatory, locked or freely selectable.

The personal workspace has a new “Notes” tab: free-form notes in a card grid (the Google Keep pattern), written with the same WYSIWYG editor as issue descriptions — selecting text brings up the formatting menu (bold, italic, headings, lists, quotes, code, links). Every note can optionally be linked to a personal task; the chip on the card opens that task's edit dialog directly.

Teloro (AI phone assistants) is now natively connected: once a call has ended, IssuePilot automatically creates a task — with a summary, contact details, category labels and a mapped priority, in whichever target team you choose. Setup takes three steps (target → connection → test), everything else lives on a page of its own.

On a shared personal board an assignment used to be silent — on a board shared by three people, nobody found out that something had been handed over to them.

The personal workspace had no settings whatsoever — profile, password, language, notifications: all of it only reachable through a team workspace. Anyone working without a team could not get at their own account.

When grouping by project, older boards put ALL open tasks under “To do” — including those whose card visibly said “In progress”. The reason: the state retrofit for existing lists only knew the done column; an existing “in progress” list quietly kept the default state TODO. It is now recognised once as well (among others “In Arbeit”, “In Bearbeitung”, “Doing”) and the tasks show up in the right section. For freely named lists the way remains the column menu → “State of the list”.

The wording of every system email used to live in the source code — every rephrasing was a code change with a deployment. The admin area now has an editor: subject, body, button label and the small note underneath, for all eleven emails, with a preview that follows as you type.

If you work in a group of three, you do not need a team with workflows, cycles and a status model — but you do need more than a board only one person can see. The personal workspace can now be shared with individual people, which turns it into the view for small groups without anyone having to do structural work.

The kanban card used to be a display: anyone who wanted to set a date, correct a title or attach a file had to open a window over the board — for a change that takes two seconds, you lost sight of the column every single time. A click now unfolds the card and makes it editable in place. The large window is still there, but only when you explicitly ask for it.

IssuePilot can now be added as a tool in Claude and ChatGPT. The AI can then evaluate, create and maintain tasks and read and edit projects and customers — right in the conversation, without copy and paste. Until now the only option was the text export “Copy for Claude”, a one-way street.

People who genuinely use IssuePilot see a discreet card above the dashboard once, asking for an honest review on a review platform. The background: platforms like OMR Reviews, Capterra and G2 rank by reviews — a profile without any sits behind everyone else, however good the product is.

Freshly uploaded files were unreliably reachable: a profile picture just set or a screenshot just attached appeared for some people while the spot stayed empty for others — in the web view as well as in the app. After a restart of the server everything was suddenly there. Anything under /uploads/ was affected, including screenshots from the widget and files in the customer portal.

On a phone a single mis-tap could paralyse the entire page: anyone who opened a row menu (“⋯”) or a filter and then tapped next to the menu to close it was stuck. The menu stayed open, and from then on nothing responded — no button, no hamburger menu, no link. Only reloading the page helped. The system admin area was hit hardest, because almost every action there runs through exactly those menus and filters.

Sign-up asked for five entries. Two of them were dispensable — and every extra hurdle costs registrations, especially with paid traffic.

cockpit.issuepilot.app was fully indexable: no robots.txt, no noindex — only the customer portal was excluded. But the subdomain is the application, not the publication; issuepilot.app is what visibility is for.

Four changes to issuepilot.app, all with the same goal: that visitors from Google ads stop disappearing again without a word.

The home page now stays the German page for everyone. Anyone with an English browser still gets the dismissible notice banner offering to switch to the English version — but no forced redirect.

The inbox gets a third tab: customer requests, between notifications and widget reports. Requests from all customers sit in one place there — you triage them without navigating to each customer first.

The customers entry now carries a number as well — just like the inbox: the workspace's open customer requests. A glance at the sidebar tells you whether something has been left lying, without opening the section.

The customer portal used to be a single page with three lists — a customer could submit a request and after that only look at a status dot. It is now a workspace of its own for your customers, with a real channel back and in the look of your workspace.

Three more areas become modules and can be switched on and off per workspace under Settings → Modules, like releases or cycles.

The timeline has been rebuilt from the ground up. Instead of a rigid monthly axis with project bars it is now a full-surface planning tool that shows everything in the workspace that has a date — and lets you change those dates where you see them.

From now on the three areas can be switched on and off per workspace under Settings → Modules, exactly like cycles, initiatives and customers. If you do not need them, your sidebar gets shorter.

Out of Kimon's testing: the screenshot was awkward and often caught the wrong window, the image editor drew far too thick and could not be moved, “full screen” produced nothing but black bars, and the contact details were gone again after every reload.

Out of user feedback: you could not see which task was currently selected, tabbing through took forever, and after ticking something off the focus jumped all the way back up to the logo.

Out of user feedback: the “Done” column and the “done” checkmark meant two similar things, and tasks could only be sorted by list. The board now knows a second axis — projects — and visibly separates the phase of work from its completion.

The personal workspace now handles the complete Google Tasks way of working, and the setup wizard explains every functional area including modules for the first time.

The result of a full browser test (Playwright) focused on light, fast operation.

Google Tasks style operation for the personal board.

The personal workspace stands entirely on its own — no mixing with the team navigation.

A new team-free area following the Google Tasks pattern: lists are columns.