Tag Archives: Bug

Bug, fixed: the Views count was incorrect in certain situations

We found and fixed a bug that reported incorrect counts for some Views (on the Home page), that was triggered when users did a particular sequence of opening a View, applying the Assigned to Me toggle, and then returning to the Home page.

It was an edge case that took us a while to figure out because our own team didn’t see the problem happen; it only affected a few users.

Views on Home Page
Views on Home Page

The counts shown on your Home Page, under the Views tab, should be correct now.

Bug, fixed: our Pricing Page wasn’t showing up correctly.

Thanks to our users in Belgium and Finland for pointing this out to us: our Pricing Page wasn’t displaying correctly in browsers that had their default language set to something other than English.

This was happening only sporadically, and only in Chrome; other browsers like Microsoft Edge were handling it correctly.

Chrome was trying to localize text for non-English users before the language resources were ready; this problem had actually been fixed in the latest version of Polymer  We are using ‘app-localize-behaviour’ of Polymer’s app-localize-behaviour (1.0.2).  Turned out we were a version behind in updating our use of Polymer.

 

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: downloading the latest version of a document, for direct sign up users

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.