A more space-efficient layout for Task Boards

We have redesigned the Task/Card details dialog to provide a more space-efficient layout, so you can see more of what you need without having to scroll:

Screenshot showing the Task Details dialog
Task Details

What used to be vertical tabs for Details, Chat, etc., is now a compact horizontal tab; this frees up a lot of space to see the details of the tags.

The other big change we made is to make the Priority setting separate from other Tags:

Screenshot highlighting position of Task Priority field
Task Priority flag

Clicking on the star will bring up your task priority options:

Screenshot showing possible values for Task Priority
Task Priority

Cards are tasks, so we are renaming cards as Tasks

If you have a engineering background, you will be comfortable calling the items that show up on Task Boards as “cards” — a term that originated with Kanban production lines in Japan, and then found its way to Scrum boards everywhere.

But for everyone else, “card” is a somewhat obscure, even baffling term, and we would often get asked a fundamental question: “what should I put on a card?

To make this clearer to folks, we are renaming cards as Tasks, because that’s what a Task/Card is: something your team needs to get done.

This is really a cosmetic change: wherever you had previously seen the word “card” you will now see either “task” or the more generic “item”.  The ADD A CARD button, for example, is now ADD NEW TASK:

And what had previously been called “tasks within cards” (or sub-tasks), is now more simply called a Checklist:

Screenshot showing a Card's Checklist
Card Checklist

Again, this is a change in terminology, not a change in functionality, but we hope it will make Kerika easier for the wide variety of users we have across the world, ranging from companies and governments all the way down to schoolkids.

Yes, we have updated our Log4J

We use Log4J mostly in our development environment, where we write new code; less so in our test environment, where we use our new code ourselves to make sure it works well (a philosophy known as “eating your own dogfood”); and only rarely on our production environment, which is where our users are.

That reflects the normal approach to debugging: you want to find problems well before they reach users.

And we are aware of the guidance from the United States Cybersecurity and Infrastructure Agency about a recently discovered critical vulnerability in the Log4J software. Naturally we acted promptly upon getting that news and updated our software on all our environments!

Tablet support

We have added tablet support for iOS and Android devices, as you can see:

The tablet experience is like that of the desktop, not the phone.

For the phone app we had to redesign a lot of the user interface to accommodate the limited screen space, but with most tablets today there is enough screen resolution to support the more extensive desktop experience.

A recent update to our mobile App

When you click on a link to a Kerika board or card in an email, that link will now automatically open in the Kerika Mobile App instead of opening in a browser tab.

This makes it a lot easier to respond to emails sent when your team members do chat on boards that concerns you: you can either do a quick reply as email itself, or, if you need more context, click on the link to open the card inside the Kerika app and see all it’s details before deciding upon your reply.