All posts by user

Bug, fixed: Exporting from a Kerika+Box board now shows user names correctly

We found a weird bug related to the export feature for Task Boards and Scrum Boards that affected users of Kerika+Box, and it has to do with the way Box keeps track of user names that’s different from the way Google keeps track of user names.

Both Box and Google ask for your first name and last name when you sign up, but their content APIs — the programming interfaces that Kerika uses — differ in the way they provide these names to Kerika.

Google gives us the first name and last name separately, e.g. it would tell us a user’s first name is “Arun” and his last name is “Kumar”.

Box, however, gives us both names together, as “Arun Kumar”, and this presents a problem because we can’t always figure out what the last name is.

And, by the way, given the wide range of cultures represented by our users, it’s far from easy to guess which part of a name is the “last name”.

For example, consider Latin American name like “Maria Beatrice Fernandez Rosario”.  Here, the last name is probably “Fernandez Rosario”, but we can’t be sure.

The bug showed up when people did exports, by appending “null” to the name — basically this meant Kerika didn’t know what the last name of the user was, and simply tagged it as “null” (which is computer-speak for “I have no idea”).

We have fixed this.

Bug, fixed: a scenario where you could have ended up with duplicate tags

We found a scenario where your Scrum Board could end up with duplicate tags. Let’s say you had a Shared Backlog which had some tags, and you also had a Scrum Board Template that had some similar tags.

If you created a new Scrum Board using that Backlog and that Template, you could have ended up with some duplicate tags, which is not at all helpful.

We have fixed this.

Dealing with new top-level domains

The growing number of new top-level domains (in addition to the old familiar .com, .org, etc.) that are available is finally starting to have an impact upon us…

While we haven’t seen a lot of use of these new domains yet, a few useful websites are starting to pop-up, e.g. using the .guide top-level domain, and this has required us to abandon an old feature of Kerika that is not going to work any more.

We used to have some validation code that checked that people were entering URLs correctly, e.g when they wanted to add a Web link to a card or to a canvas.

This validation is pretty much impossible to do in the old form, because of the rapid proliferation of new top-level domains, so we are dropping that validation feature which was kind of nice to have…

Android tablet experience improved

We have been doing a bunch of testing and bug fixing related to using Kerika on Android tablets.

As with iPads, you don’t need to install a special app in order to run Kerika: you can just use the Chrome browser on an Android tablet to access Kerika, and use your finger to move stuff around just as you would with a mouse.

We found an fixed some problems with the Chrome touch interface; the overall experience should be a lot better than it was before!

Note: you are almost always better off using the Chrome browser rather than the standard browser that comes with all Android tablets; that’s because Google has a lot more enthusiasm for improving their proprietary (non open-source) products than “stock Android“.

Why, yes, Kerika did get faster

If you are wondering whether Kerika is faster than it used to be, yes, it is.

We made a change in our software architecture — the way each board would connect to the server and ask for all its cards and all the updates on these cards — that has reduced the total upload of data.

This was actually a significant improvement in upload speed: about 10x.

Since upload speeds are frequently much slower than download speeds, even on broadband connections, this should help load larger boards much faster.  And on mobile connections this should help reduce the amount of data consumed.

By Invitation Only: clarifying privacy settings on your Kerika boards

We made a small label change that we hope makes it clearer what your choices are for managing the privacy of your Kerika Task Boards, Scrum Boards or Whiteboards: “By Invitation Only”.

We used to have a setting that we had labeled “Team Members and Visitors”; it came with some help text that we thought clarified the issue, but which didn’t work well enough for everyone — as we found out through our ongoing conversations with users.

This is what it used to look like:

Team Members and Visitors
Team Members and Visitors

 

It turned out that not everyone was reading the help text that appears just below the choice for “Team Members and Visitors”.

So, we are tweaking the choice to say “By invitation only”, which we hope will be more self-explanatory.

By invitation only
By invitation only

Sometimes the best usability improvements come from just changing a few words…

From Export as CSV to Export as Excel

We used to have Export as HTML and Export as CSV as options for our Task Boards and Scrum Boards, and with our latest version we are tweaking the Export as CSV to become Export as Excel instead.

There are a couple of reasons we did this:

  1. We now include chat and document links in the export: this was done specifically to help our many government users who need to respond quickly to Freedom Of Information Act (FOIA) requests.
    (See our separate post on how Kerika makes FOIA-compliance one-click easy.)
  2. Everyone who uses the CSV export wants the data to end up in an Excel file anyway, so why not put it in that format to start with? (After all, it’s easy to go the other way as well, from Excel to CSV…)

Export as Excel

Export as Excel

The Whiteboard Daily Digest: a feature that died quietly, a long time ago

A long time ago we used to have a feature we called the “Daily Digest” which sent an email everyday summarizing all the changes that had been done to your Whiteboard projects overnight.

(This was back before we added Scrum Boards and Task Boards as a feature, when all we had was our patented Whiteboards.)

We never got this feature to work properly: not because it was buggy in a technical sense, but because we could never figure out how to make it a useful feature.

After trying numerous times to tweak it we finally gave up a long time ago.

And promptly forgot all about it.

It turns out that the feature had only been turned off on our server software; it hadn’t actually been ripped out.

We stumbled upon it in an obscure corner of our vast code base recently and were surprised to find it still there, albeit in a “commented-out” form.

Well, it’s gone for good now. It never worked well, it had been turned off for years, and now it’s in the trash…

What happens if you have a Kerika+Google and Kerika+Box account, in the same name?

As you know, we offer a great integration with both Google Drive and Box, giving you the choice of using either of these cloud storage services when you sign up as a Kerika user.

For most people, the choice of whether to use Google or Box is often made by their employer, whose IT departments may have already developed a cloud strategy for their organization.

For a small number of people, particularly those in organizations that haven’t committed to a particular cloud strategy yet, they do have the choice of using either cloud service, or even both.

So, what happens if you have the same email address, e.g. someone@example.com, and you set up a Google ID and a Box ID that use this same address?

You could end up with two different Kerika accounts that use the same someone@example.com ID: that’s because each sign up, from Google and from Box, takes a different path into Kerika.

This is not a great situation to be in, and we certainly don’t recommend it, but the software does try to behave well when confronted with this situation.

If another Kerika user invites you to join her project team, the invitation will show up in both your Kerika+Google and your Kerika+Box account — and in your email, of course — but when you try to accept the invitation Kerika will check to make sure you are logged into the correct service.

Here’s an example: Jon, who uses Kerika+Google, invites Arun to join one of his projects. Arun happens to have both a Kerika+Google account, and a Kerika+Box account, but Jon doesn’t know that — and he shouldn’t have to care, either!

When Arun sees the invitation, he happens to be logged into his Kerika+Box account:

Invitation received on Kerika+Box account
Invitation received on Kerika+Box account

 

But when he tries to accept the invitation, Kerika checks to see whether Arun and Jon are both using the same cloud service, and discovers that Arun is logged into his Kerika+Box account and not his Kerika+Google account:

Prompt to login to Kerika+Google account
Prompt to login to Kerika+Google account

 

So, Kerika works behind the scenes to help Arun sort out his two accounts.