Tag Archives: Bug

About bugs we found and fixed.

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

Agile & Scrum, Bug Fixes, , , ,

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

Bug Fixes,

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.

Bug, fixed: downloading the latest version of a document, for direct sign up users

Bug Fixes, Technology, ,

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.

Bug, fixed: Handling the newer top-level domains

Usability

One of our users pointed out that Kerika wasn’t allowing people to be invited if their email addresses were from one of the newer top-level domains that are being used: e.g. “.build”.

We have fixed that.  The problem was the client software had some validation rules, written a long time ago, that checked for three characters to appear after the “.” in the end of an email address.

That’s obviously not a good idea anymore, now that there are dozens of top-level domains…

A bunch of bug fixes and usability improvements for Tasks

Agile & Scrum, Kanban & Lean, Kerika, Usability, , ,

We have done a bunch of small bug fixes and usability tweaks to the Tasks feature we introduced a few weeks ago:

  • When a user’s last Task within a card is marked as Done, the user’s name is removed from the list of people shown as being assigned to that card. (Previously you had to do this cleanup manually.)
  • When a Task that was previously marked as Done is changed to be “undone” (open/remaining), the user who had previously been assigned to that Task is added back to the list of people shown assigned to the card.
  • Bug fix: If someone is assigned to a Task, and this person had previously completed a Done Task, this user wasn’t getting added automatically to the list of people shown on the card. This has been fixed.

 

Bug, fixed: Custom Highlights were getting carried over from one board to another

Agile & Scrum, Kanban & Lean, Usability, , ,

We fixed a bug that was kind of annoying: if you had a Custom Highlight defined for one board, and then switched to another open board, the Custom Highlight was getting applied automatically to the second board as well.

This happened only if people used the Board Switcher button that appears on the top left of the Kerika app:

Board Switcher
Board Switcher

The Board Switcher keeps track of all your open boards and is a fast way to switch between them if you are working on several different projects at the same time — you don’t have to go back to the Home page to find your boards again and again.

Every of your open boards can have Highlights set, or not, as you like. This bug fix makes that a smoother process.

Bug, fixed: Apparently 40 characters wasn’t enough for a name

Bug Fixes, Technology, Usability

Unexpected bug we encountered recently: an attempt to sign up as a Kerika user, using our direct sign up process, failed.

When we looked into the error logged on our server, we discovered that this user was trying to enter a first+last name combination that came to 42 characters; our code assumed that no name would exceed 40 characters in length.

Digging a little further into the user scenario, we discovered that these were accounts that were being opened in the name of organizations, or departments within an organization, rather than actual people.

So while 40 characters may have been enough for most “real people” names, it wasn’t enough for department names, e.g. something like “Kerika Marketing Communications Team”.

Live and learn.

Bug, fixed: now the Board Summary excludes cards in Trash

Bug Fixes, Usability,

Thanks to one of our users from Washington State’s Administrative Office of the Courts for pointing this out: it turned out that the count of “remaining” cards in the Board Summary was including items that were in the Trash, which was misleading.

This has now been fixed: the count shown in the Board Summary gives you a better idea of what work remains.

To access the Board Summary on any Task Board or Scrum Board, click on the Board Summary button shown on the top-right of the Kerika app:

Board Settings is highlighted
Board Settings is highlighted

Clicking on this button will show a summary of the board, like in this example:

Remaining work
Remaining work

In the example above, the count of “28 items remain” now properly excludes any items that are in the board’s Trash.