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.
Here’s an example:
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.
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 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.
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:
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!
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:
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!
We recently discovered (and fixed) an annoying bug that was affecting the Shared With Me view of boards and templates that your colleagues shared with you.
If a colleague created a new template that they intended to share with their Account Team, this new template wasn’t appearing correctly in this view. That’s been fixed now.
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.
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:
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.