Changelog

Discord integration improvements

• Even if you set the reaction threshold for creating cards to 0, Decky will add a specified reaction. For commands without a configured reaction, it’ll default to the ✅ reaction.
• Allow leaderboards for commands with a threshold of 0.
• Spread leaderboards over several messages if it grows too large for a single message. (If you’ve missed Decky posting a leaderboard, that issue was probably the reason why.)
• When creating a leaderboard, Decky checks whether any changes have happened compared to the last leaderboard. If that wasn’t the case it’ll still repost that leaderboard if someone else has posted in the channel in the meantime.

Search update

Our internal search system has been completely rewritten. It doesn’t look too different from the outside but comes with quite a few benefits for you:

• Performance: Instead of loading all relevant cards into the browser and performing the search on your machine, the filtering now happens directly in the database, leading to much less data that needs to be exchanged.
• Completeness: Includes all cards in search even when the current scope contains more than 3000 cards.
• Card references: When searching for cards when typing $[card title] in the editor, it’ll search for all cards not just a subset of 3000 cards.
• Search: When entering multiple values of the same category, i.e. multiple owners, it now performs an ‘or’ search rather than and ‘and’ search within that category.
• Search: Include search options for No owner, No milestone, No deck and No project
• Swim lanes: Clicking on a swim lane label will add a search filter for the lane, so you can drill down further

Here’s some presents from us for some merry holidays:

• Animations: Reworked the underlying animation engine to prevent stuttering animations.
• Archived Cards: Non-done cards that got archived get a dedicated color so they’re easier to differentiate from their non-archived counterparts.
• Attachment Viewer: Now includes the title of the images.
• Github/Gitlab/Bitbucket Integration: You can now mark multiple cards as fixed by including e.g. Fixed $123, $124, $125 as part of your commit message.
• User Management: An updated look and improvements for bigger user lists.

A few fixes for you:

• 1,2,3 shortcuts: The hover-and-hit-a-number feature for updating a card’s priority and effort now also works for the card detail view. To avoid accidental tab navigation, we changed the 1, 2, 3 shortcuts for switching to the Hand, Decks and Milestones tab with Shift+1, Shift+2, Shift+3.
• Time Tracking: Improved behavior when hitting the + and - buttons in the timer widget at the bottom. You can also reset the timer to zero when hitting the - button often enough. (By the way: did you know you can keep the buttons pressed for faster updates?)
• Tooltips: Tooltips that would open close to the bottom of the screen sometimes led to scrollbars appearing. Not any longer!
• Auto Archive: We no longer auto-archive done cards with open comment threads.
• Deck Picker: The cover images disappeared! But we found them and put them back into their place.
• Stability: The last release led to crashes on Safari and Edge Browsers when trying to open overlays, this was fixed.

This release contains all necessary changes to migrate away from our existing CRM provider (Mailchimp) to a self-hosted solution. This means your data will be shared with one service provider less. (Leaving only our payment provider Stripe and our hosting solution.)

Big performance update 🚀🚀🚀

After adding and refining a lot of features, we felt it was time to focus once again on one of our major core values: A snappy and responsive interface. Teams with a lot of cards and decks might have recognized that it might take a second or two to load the deck library in a new tab. Same for opening a deck for the first time.

So we took the time to put our profiling goggles on and to look for all cases in which the browser is doing more work than it should. We found a lot of opportunities for improvements and updated our card, deck, deck library and notification components with performance improvements in mind. We feel it’s been well worth it! Loading up the deck library in a new tab has been sped up by a factor 3 to 4!

Notification updates

Before this update, notifications were generated on the fly, in your browser by checking all relevant card changes. This approach led to some performance issues for projects with a lot of activity. So we improved it significantly by generating notifications on the server instead. This should speed up a lot of interactions that could potentially generate notifications.

But this update did not only improve performance but came with a lot of new features as well:

• Dismiss all: a.k.a. declaring notification bankruptcy 📉. By holding down the dismiss button in one of the three notification groups (cards you own, cards you’re subscribed to, conversations) you can remove all notification at once.
• Snoozing conversations: Previously this notification wouldn’t show up if some conversation participant still had an open notification for this conversation. Not ideal if one of the participants wouldn’t check (and dismiss) their notifications on a regular basis. Now it’s always shown to all participants after some inactivity on the thread.
• Subscribing to cards: You’re automatically subscribed to a card if you’re the card creator or if you’re mentioned on a card. (Yes, we’ll definitely plan on adding an interface to let people know who is subscribed to a card and allowing them to unsubscribe.)
• Notifications for mentions in cards: This is actually more of a bug-fix. Before, you would only receive a notification for being mentioned on a card if you were observing it (via deck or card subscription). Now you’ll always get a notification if you get mentioned in a card’s content.
• Group notifications by milestone & deck: When multiple cards are moved to a new milestone or deck, it’ll generate a single notification pill instead of one notification pill per card.
• Last participant notification: If everyone left a conversation except you, you’ll now get a notification.

Export cards as csv

Once you start selecting cards, you’ll find a download icon in the right part of the selection bar. Here you may pick the desired fields to export and download a csv file right away!

Time Tracking

We’re super stoked to announce that this release introduces time tracking!

Open up the Mission Control and navigate to Organization Settings > General and look towards the bottom for the relevant settings. Time tracking comes in two flavors: Manual mode and Real-time mode.

Manual mode allows you to enter your time manually via a card’s history panel.

The Real-time mode allow you to manually enter your time as well, but comes with a lot more power: it will be tracking your time whenever you start a card. This basically means, if a card a blue, you’ll be tracking time. To reduce any confusion this also means that a single user can’t have more than a single started card. So you might have to adapt your workflow if you want to activate this feature. But we strongly believe it’s worth it as a blue card will be a strong signal to your team that you are actually currently working on this card.

• Milestones: When displaying the amount of days left, we now use actual working days. They default to Mo-Fr, but can be customized in your organization settings.
• History panel: Changes to your card content now result und much improved diffs in the history panel.
• Drag and drop: When ordering by project tags and drag and dropping a card into a new swimlane, the tag won’t be appended to the card’s content. The project tag will directly be applied instead.
• Performance: Whenever you performed an action, all your and your team mates’ Codecks browser tabs received a message to fetch fresh data at the same time. This meant that the database had to reply to a lot of request simultaneously, leading to a performance bottleneck. This has been changed such that messages to other tabs are now deferred and spread out such that the tab performing the action gets a quick response before other tabs request fresh data.