Tag Archives: Task Board

About Task Boards. See also Kanban and Lean.

Guarding against XSS/code-injection

It’s possible to copy-paste text into a Kerika Chat message, and there are legitimate use-cases for this: for example, a developer may ask a question to a coworker who replies with a code snippet.

Kerika handles code in chat messages by storing two versions of the message: as plain-text, and as the original format. When a chat message is displayed, the original format is used but not executed, which means the embedded code is visible, but doesn’t run in the browser. This makes it easy and safe to share code snippets through chat messages.

While making this improvement, we went through all the places where a user can type in text, Card Title and Description, Board Name and Description, Tag, Attachment Name, etc. to make sure we are guarding against malicious code injection.

An easier way to search for cards by number

Along with the recent improvements we made to the Auto-Number Cards feature for Task Boards and Scrum Boards, we have also made it easier for you to search for cards by their number.

It’s simple to use: just type in a number in the Search box on the top of the Kerika app and Kerika will assume you are looking for a card with that number. It will also search for anything else with that number, but will prioritize a card matching that number as the first result it shows.

An improvement to our Views function

We just updated Kerika today, and along with the usual bug fixes and other behind-the-scenes stuff we have made an improvement to the way Views are shown on your Home Page:

Improved Views in Kerika
Improved Views in Kerika

Some of our users have dozens of boards in active use at the same time, with large (and sometimes overlapping) teams, and as a result their Views counts are nearly always high.

As you can see from the screenshot above, the Home page now shows two counts for each View:

  • The total number of items that match for that View, and
  • The number of items that match that are assigned to you.

This makes it easier to see if you need to go back to a View to catch up on something that’s directly related to you, i.e. is assigned to you.