Monthly Archives: December 2021

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.

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.

Moving entire columns of tasks (cards)

We have added a new function to let Board Admins and Team Members move an entire column of tasks (cards) with a single action, within a single board or across multiple boards in the same account.

The function can be accessed by from the  menu that appears as a pop-up when you click on the dots on the top of each column, as well as when you use the right-click mouse action on any cards:

Screenshot showing the Task Options menu
Move entire column

If you choose the Move to another column action, a pop-up dialog appears that lets you choose the column you want to move these cards to:

Screenshot showing the Move to Another Column dialog
Move to another column

If you choose the Move to another board action, a new dialog appears that lets you choose the board where you want these tasks to go to:

Screenshot showing moving cards from one board to another
Move to another board

After selecting a destination board, you can then pick the exact location of the column you are moving, relative to the columns that are already on that board.

And, as you can see, from the screenshot, you are also able to move columns from boards in one account to another account where you are also an Account Member.

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!

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!