We added a feature recently (or did we actually a bug?) for our direct login users: when you reference a file that’s attached to a Kerika card, canvas or board, from another place in Kerika — e.g. another card’s details or chat — we now show the file’s name instead of just the URL.
This makes it easier to cross-reference file attachments from within different Kerika cards or boards, where different work items or conversations refer to the same shared file.
With the proliferation of top-level domains we have had to update some of our old code that tried to make sure people were signing up with properly-specified emails.
In the old days, of “.com” and “.org” and other short domain extentsions, this was easy to check at the time someone entered an email address: if it wasn’t properly formatted we could alert the user right away so they didn’t go down a dead-end path.
We can’t do that anymore: new top-level domains are being launched on a regular basis by registry companies and the list of potential domain extensions is no longer finite or easily matched by regular expressions.
If you create a list of tasks on a card on a Task Board or Scrum Board, Kerika does a bunch of stuff in the background to make sure your view of what’s due, at the card level, board level and account level, are always correct.
We found a couple of edge cases where the due dates on tasks wasn’t rolling up correctly to the card level, potentially giving users a misleading view of what was currently due for them:
When the last task with a scheduled due date was removed (deleted) from a card, this wasn’t correctly adjusting the due date for the card itself.
Similarly, when the last task with a scheduled due date was no longer scheduled, this wasn’t correctly adjusting the due date for the card.
Both bugs have been fixed. They were real edge-cases, so it’s likely that most users never noticed them in the first place, but still…
Internet Explorer continues to be slightly offbeat in its behavior, and this trips up our testing since it still has some quirks that are not found in Chrome, Firefox or Safari.
One bug that one of our Norway-based users found was that he couldn’t copy the details of a card using the Ctl-C key combination while using Internet Explorer, without going into the edit mode of the card details.
We fixed that. Ctl-C and Ctl-V should work much better.
We used to offer monthly and annual subscriptions, and in the last 5 years we had just two customers ever request the monthly option.
Everyone else found the annual subscriptions far more convenient so they wouldn’t have to process invoices or receipts, or get internal purchase approvals, every month.
The monthly purchase offer wasn’t very good for Kerika either: there’s a certain amount of bookkeeping and overhead for processing every invoice and given the already low $7 price per user, this offer was essentially a money-losing proposition.
So, we are now discontinuing the monthly subscription purchases altogether. We are asking all our customers to purchase annual subscriptions: the amounts involved are still very reasonable, and if you do change your mind in the middle of the year, you can still request a refund for the unused portion of your annual subscription.
This means you don’t have an risk of overbuying: if you change your mind about using Kerika, you can get a refund for the remaining portion of your subscription.
Thanks to our users at Oxbow Farm, we have found and fixed a bug that affected users who signed up directly with Kerika: clicking on an attachment in the card details was downloading the original version of a file, not the latest.
Here’s what was happening: when you add a file to a card or canvas, Kerika checks to see if that file was already being used on that particular card or canvas. If so, Kerika automatically handles your latest upload as providing a new version of the old file, so you see just one entry in your card attachments view:
The bug that we recently discovered, and fixed, resulted in Kerika downloading the original version of the file when you used the download option that appears after you select an attachment from the list of attachments on a card.
If you clicked on the attachment’s thumbnail to open a preview of the file, Kerika was correctly opening the latest version of the file. The bug was only in the download action, and that’s been taken care of now.
We have made a bunch of improvements to the Contact Us feature in Kerika, which — as before — can be accessed by clicking on the help button (“?”) in the top-right corner of the Kerika app:
Previously this simply opened up your local email client to send us a message; now the feature is built into Kerika itself, and is smarter about how it works.
When we analyzed our old trouble tickets, and emails to email@example.com in general, we found there were very few instances of actual bugs being found, but more commonly there was some confusion about how Kerika was working for the users.
And very frequently when people got in touch with us, they didn’t include important information in their original emails that would help us understand what problem they were currently facing.
This meant we had to reply back to ask them some common questions, like “have you already invited this person to join your board?”, and this led to unwelcome delays in resolving the problem for our users, especially when they were located many time-zones away and there was a 24-hour delay before they replied, and then we replied, and so on.
Our new Contact Us dialog, while very simple in appearance, acts as a smart collector of key information that can help us understand the context of the user’s query:
Who is part of this board team right now? Again, this isn’t something we would know without being told by the user, since we don’t have any easy way to look at someone else’s boards. If you think you have added someone to your board, but haven’t yet, this can help us clarify any misunderstanding on your part.
What’s the current state of your Inbox and Sentbox? Are there invitations waiting for you to accept that perhaps got missed, because they unfortunately ended up in your spam folder? Are there invitations that you had previously sent to coworkers, that haven’t been accepted yet?
What’s your current computer environment? What operating system and browser are you using? In the very few instances when someone reports an actual bug, it’s very important to know which browser and OS they were using, since the bug may be limited to a single environment.
And, finally, the Contact Us process reminds our users that any intermittent problem they are facing can often be resolved simply by refreshing their browser: if they had experienced any fleeting network problem or latency that interfered with their Kerika view, a simple browser refresh will fix that quickly.