UI tweaks: new icons to allow for a future feature

At the time we added “In Progress” as a new status value, we also removed the “Done” status, mostly because the drop-down list of status choices was becoming rather long — and “Done” was not quite like all the other choices that we were presenting for marking a card’s status.

This is what the old choices looked like:

Old status values
Old status values

And this is what the new status choices look like:

New icons for status settings
New icons for status settings

There are two small UI tweaks here that we made:

  • A purple color is now used for “Needs review” — this previously was green, but green was really the best choice for “In Progress”, and we didn’t want to use the same color for two different states.
  • The icon for “Critical” has been changed to look like a fire: that’s because we want to reuse the old triangle icon in the future for a great new feature that we are still brainstorming — a way to mark certain cards as “troubled”.

UI tweaks: avoiding errors in the right-click menu

Building a great user experience is rarely the result of big, bold actions: more often it is the cumulative gain of a large number of very small tweaks we make to our user interface design.

Here’s an example: the right-click menu, when you click on a card on a Task Board or Scrum Board, used to look like this…

Old right click menu
Old right click menu

This menu is a little crowded, and one irritating source of errors was that people would sometimes click on one of the Move choices (Move to Done, Move to Trash or Move to Backlog) when they intended to do click on one of the others choices instead.

The irritation came from the fact that these Move operations had a much bigger impact than the others: for example, if you accidentally cut a card, you can reverse that operation by selecting the cut cards once more, which would effectively “undo” the cut.

But, if you move a card to Trash or Backlog, it was a lot more hassle to get it back: you had to make sure the Trash or Backlog was currently being displayed — and in many large boards these columns are routinely hidden from view by the user — and then find and drag that card back to where it was.

So, here’s our small UI tweak to reduce the chances of this error:

Right-click menu has new styling
Right-click menu has new styling

A simple visual cue, in the form of grey horizontal separator lines, helps remind the user that some of these right-click mouse operations are “more significant” than others, by creating a visual segregation of these options from others.

A simple UI tweak that helps reduce errors by our users, and one that adds up to a great user experience!

 

UI tweaks: Making it easier to restore Archived Projects

In a long, endless series of UI tweaks that are each small in themselves, but which we hope will collectively add up to a great user experience…

We made it easier for Account Owners to restore archived projects and templates:

Restoring from Archive
Restoring from Archive

This button is shown only to Account Owners, since the power to archive a project or template, or to restore an archived item, is restricted to the Account Owner.

An improvement to Card History

Every card, on every Kerika Task Board or Scrum Board, contains within it a full history: a log of all the changes that have been made to it.

(A few actions are ignored because they can occur so often, and are often inconsequential, e.g. moving a card up/down within the same column. In contrast, moving a card across columns is considered consequential, and is therefore logged in the card history.)

We recently made a usability improvement in the way the Card History appears: the log of changes is now shown in chronological order, rather than reverse chronological as was the case before.

This makes history look more like chat, and should make it more usable!

Making sure all Project Leaders are equally empowered

On any Kerika Task Board, Scrum Board or Whiteboard, you can have as many Project Leaders as you like.

(Normally, teams prefer to have just a single Project Leader, but sometimes it is helpful and appropriate to designate more than one person as Project Leader; among other things it provides redundancy, so that the single Project Leader doesn’t become a bottleneck for handling requests.)

Just how active a Project Leader is depends upon the dynamics of the team: in some teams the Project Leader is just an administrative role, filled by someone who is like a Team Member in every other respect in terms of how much work she takes on, while in other teams the role may be more formal.

It turned out there was a bug in how Kerika handled notifications and requests when there were several Project Leaders on a single board: these notifications and requests were getting routed to just one Project Leader instead of all of them, so there was still a potential for having a bottleneck.

With our latest release we have fixed that problem: now, all notifications and requests get routed to all Project Leaders, so any of them could act upon it. This should remove the bottleneck!

Easier to tell who moved a card to your board’s Trash

When a Team Member deletes a card, it just gets moved to the board’s Trash; it doesn’t get immediately deleted from Kerika’s database even though it disappears from your view right away.

That’s because the “delete” action in Kerika is really a “move to Trash” action: you are removing something from view, but not necessarily getting rid of it for good.

Any Team Member can delete a card, but only a Project Leader can completely and permanently get rid of it — in other words, “taking out the trash” is one of the privileges reserved for Project Leaders (and Account Owners).

The Trash column is normally not shown on your Task Board or Scrum Board, but you can bring it view easily by clicking on the Filter button:

Making Trash visible
Making Trash visible

 

With our latest version, it’s easy to see who moved the card to the Trash: we show this right on the card itself.

Seeing who deleted a card
Seeing who deleted a card

“In Progress”: a new Kerika feature

We are adding “In Progress” as a new status tag for cards, on Task Boards and Scrum Boards, that we think will make it easier for everyone to see which items are actually moving along.

In Progress
In Progress

Couple of reasons why we did this:

  • People get assigned too many cards sometimes, even when they are working with a “Pull” model (as opposed to “Push”), sometimes even using Work-in-Progress (WIP) Limits don’t solve the problem of easily seeing exactly what’s being worked on at any time.
Template example
Template example

In this process template, we have three buckets of activities: Background Check, IT & Facilities Setup, and Onboarding, and we have a separate In Progress column that you could use to indicate which card is currently in progress.

But, with a “In Progress” status indicator on cards, you wouldn’t need that extra column: you could work on cards from any of those three buckets and indicate their status right there. And when the work gets completed, these cards can go straight to Done!

Bug, fixed: handling filenames with Cyrillic characters

A Russian user kindly alerted us to a bug that we have now fixed: filenames that used Cyrillic characters were not getting uploaded correctly, because of an encoding problem.

The problem had to do with Kerika not using a sufficiently large character set, which resulted in some languages not being supported properly.

We have fixed that by moving away from the UTF8 character encoding to UTF8MB4, which is an encoding format used by MySQL databases.

UTF8 uses a maximum of 3 bytes per character, which limits the range of languages that can be supported.  UTF8MB4, however, uses a maximum of 4 bytes per character which considerably extends the range of possible characters.

Distinguishing between “Rescheduled to” and “Scheduled”

As we were “eating our own dogfood” with the new Planning Views feature, we increasingly found a need to distinguish between cards that had been scheduled for the first time, and those that were being rescheduled because they didn’t meet their original due dates.

This was probably a useful distinction for us to have made even before now, but the new Planning Views made it really important to tell which cards were slipping and which weren’t, and anyway, that’s the whole point of “dogfooding”: we use what we build, extensively, before we give it to our users, and that’s how we make great software :-)

So here’s a simple enhancement that we think will help all teams: if a card on a Task Board or Scrum Board is rescheduled, i.e. given a new due date, the card will flag that like this:

Rescheduled Due Date
Rescheduled Due Date

As soon as you click on the card, the orange highlight gets turned off, and the due date is shown like any other date:

Regular Due Date
Regular Due Date