Seeing at a glance what’s hidden

If you hide a column from your view of a Task Board or Scrum Board, Kerika now makes it clear whether this column has any cards or not:

Hidden columns
Hidden columns

In the example shown above, the Release Notes column is empty, so it is shown in a light shade of grey, while the Final Review column has at least one card, and it is shown in black.

Kerika also helps you see, at a glance, whether the columns you are hiding have any updates you haven’t caught up on, or cards that are overdue:

Hidden columns with updates and overdue dates
Hidden columns with updates and overdue dates

The orange icon in the example above shows that the This Sprint column contains cards with updates on them that you haven’t caught up on yet, and the red icon shows that the Planning column contains overdue cards.

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.

Wrestling with SSL certificates

We had previously been using SSL certificates for our website (kerika.com) and this blog (which is on a subdomain: blog.kerika.com) that we got from GoDaddy, but we have moved away from them.

What pushed us away was their aggressive approach to billing customers: they automatically renewed our SSL certificates after just 9 months into a 12-month contract, which we found unacceptable.  Talking to their customer service people was an unhappy experience as well, so we decided to not do any more business with GoDaddy.

Now we are using a SSL from Amazon for our website and app (kerika.com): Amazon actually provides free SSL certificates to sites hosted on Amazon Web Services, and it was easy and simple to set up.

However, AWS doesn’t provide wildcard SSL certificates so we couldn’t handle our blog as well — particularly as our blog isn’t hosted at AWS. Instead we got a SSL certificate for the blog from RapidSSL which is reasonably priced.

So far, so good.

A style refresh for our Blog

Hope you like it — we finally got around to customizing the WordPress TwentyThirteen theme we have been using for this blog.

Nothing fancy; just making sure the colors and font (especially the fonts!) are consistent with our website and app.  We use Roboto everywhere now: we find this to be a really easy to read font for most screens, and think that Google did a great job in coming up to an alternative to the traditional Arial/Helvetica.

We are also trying to clean up the Categories and Tags we use to help you find older blogs: there were too many overlapping categories/tags that had accumulated over the years so we got rid of a bunch of them.

Let us know what you think…

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!

We made it easier to have more complicated tasks inside cards

When we first added the ability for you to add a list of tasks to a card on a Task Board or Scrum Board, our expectation was that these tasks would be short and to the point: maybe just a few words long.

And to make the display of tasks neat and tidy inside a card’s details view, we truncated long tasks to show just two lines worth.  We figured this was a reasonable restriction that would make the layout look better, and wouldn’t actually inconvenience anyone since we really didn’t expect people to create very complex tasks, that might take more than one sentence to spell out.

Well, that turned out to be a bad assumption: the tasks feature turned out to be far more popular than we expected, and we soon started getting complaints from people that didn’t like seeing their tasks get truncated to two lines.

We have fixed that with our latest update to Kerika: now, all tasks will show fully, no matter how long they are. Here’s an example:

Example of long task
Example of long task

In the example shown above, the first task is long enough to spill out over three lines, and all three lines are shown.

So, there you go: tasks became a little more flexible!