All posts by user

Switching to Let’s Encrypt for our SSL certificates

We have mentioned below the problems we had with GoDaddy’s SSL certificates; we have fixed this by switching to the open-source certificate authority called Let’s Encrypt.

Lets Encrypt SSL
Lets Encrypt SSL

Let’s Encrypt is a free, automated, and open certificate authority brought to you by the non-profit Internet Security Research Group (ISRG). It lets us host our own certificates, so we don’t have to rely upon third parties and can have better control over the quality of our service.

We have added support for Google Team Drive

We have long had a deep, excellent integration with Google Apps: you can sign up with your Google ID and have all your Kerika-related files stored in your own Google Drive, where you can access them independently of the Kerika app.

We are now taking that one step forward, with seamless integration with Google Team Drive.

Google Team Drives are shared spaces where teams can easily store, search, and access their files anywhere, from any device.

Unlike files in My Drive, files in Team Drive belong to the team instead of an individual. Even if members leave, the files stay exactly where they are so your team can continue to share information and get work done.

Team Drives is available on G Suite Enterprise, G Suite Business, or G Suite for Education editions.

You don’t need to do anything different: the integration is built-in with the latest version of Kerika (and, since we are software-as-a-service, everyone always uses the latest version of our product!) and the integration is seamless.

Managing multiple versions of files just got a lot easier

With our latest update we have made it much easier to manage different versions of files, across all your Task Boards, Scrum Boards and Whiteboards.

(This was inspired by our recent fix to a bug that didn’t properly download the latest version of a file attached to a card or canvas; while fixing this we started thinking deeper about how to make file management even easier for our users.)

Here’s how file management works now: when you hover your mouse over a file attachment, a new action called +NEW VERSION is available:

Uploading new version of document
Uploading new version of document

Clicking on the +NEW VERSION button will let you pick any file from your computer that’s of the same type, and Kerika will add that and track the file as a new version of your old attachment.

This is possible even if the new file has a different name altogether, as long as the two files are of the same type.

For example, a filed called Budget.xlsx can get a new version that’s called Plans.xlsx — both are tracked as different versions of the same file, even though they had different names.

This makes it even easier to manage all your files using Kerika!

Bug, fixed: signing up for Kerika from “.software” domains

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.

We thought we had done these updates a while back, but clearly something slipped through the cracks: people from “.software” domains were unable to sign up as new users.

That’s fixed now.

Bugs, fixed: edge cases where due dates on tasks weren’t being reflected correctly at the card level

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:

  1. 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.
  2. 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…

 

Bug, fixed: copy-paste of card details in Internet Explorer

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.

A bunch of bug fixes

We have been busy through the holiday season, as usual, but there isn’t a lot of stuff to show you yet since the big new thing we are working on — a more automated and efficient account management and billing system — won’t be ready for a while.

Meanwhile, we have been working through bug fixes on a regular basis; many of them obscure and probably unnoticed by anyone but the Kerika team itself, but we don’t like to have known bugs sitting around so we knock off bugs fairly quickly even if no one has complained (yet).

Here are some of the bug fixes we have done recently (in no particular order):

  1. A problem that affected direct sign up users who wanted to preview their documents, but didn’t allow third-party cookies to be set in their browsers.
  2. An obscure situation where someone who owned a board, but wasn’t part of the board team, shared it with another user: in some situations the second user didn’t see this board listed correctly in their Shared With Me tab of their Home page.
  3. Another obscure circumstance in which a board owner’s face wasn’t shown correctly in the Shared With Me tab of other users.
  4. Helping a user restore access to a board that had gotten corrupted somehow in the database: this wasn’t the user’s fault and we wanted to make sure no work was lost.
  5. Some improvements to labels used in My Preferences to clarify (better) the user’s choices.
  6. Fixing at least one situation where someone wanting to sign up with their Google ID (as a Kerika+Google user) was getting endlessly redirected by Google and never reaching Kerika.  (For some reason everyone who reported this problem is located in Norway; don’t know why…)
  7. A problem affecting direct sign up users: they weren’t seeing thumbnails of their files in their Kerika cards and canvases.
  8. Some situations where a browser left running Kerika overnight didn’t refresh itself automatically the next morning, and required the user to manually refresh the view.
  9. A bug that kept cards with Critical priority from showing up correctly in the What Needs Attention View.
  10. Decided to spell “synch” as “sync” in the Calendar dialog, although we still don’t agree that “sync” is a better spelling than “synch”.
  11. Numerous updates to our website: our product’s functionality keeps expanding so fast that we need to remember to update our website every few months!

Happy New Year!