We added a feature recently (or did we actually a bug?) for our direct login users: when you reference a file that’s attached to a Kerika card, canvas or board, from another place in Kerika — e.g. another card’s details or chat — we now show the file’s name instead of just the URL.
This makes it easier to cross-reference file attachments from within different Kerika cards or boards, where different work items or conversations refer to the same shared file.
We have long had a deep, excellent integration with Google Apps: you can sign up with your Google ID and have all your Kerika-related files stored in your own Google Drive, where you can access them independently of the Kerika app.
We are now taking that one step forward, with seamless integration with Google Team Drive.
Google Team Drives are shared spaces where teams can easily store, search, and access their files anywhere, from any device.
Unlike files in My Drive, files in Team Drive belong to the team instead of an individual. Even if members leave, the files stay exactly where they are so your team can continue to share information and get work done.
You don’t need to do anything different: the integration is built-in with the latest version of Kerika (and, since we are software-as-a-service, everyone always uses the latest version of our product!) and the integration is seamless.
With the proliferation of top-level domains we have had to update some of our old code that tried to make sure people were signing up with properly-specified emails.
In the old days, of “.com” and “.org” and other short domain extentsions, this was easy to check at the time someone entered an email address: if it wasn’t properly formatted we could alert the user right away so they didn’t go down a dead-end path.
We can’t do that anymore: new top-level domains are being launched on a regular basis by registry companies and the list of potential domain extensions is no longer finite or easily matched by regular expressions.
If you create a list of tasks on a card on a Task Board or Scrum Board, Kerika does a bunch of stuff in the background to make sure your view of what’s due, at the card level, board level and account level, are always correct.
We found a couple of edge cases where the due dates on tasks wasn’t rolling up correctly to the card level, potentially giving users a misleading view of what was currently due for them:
When the last task with a scheduled due date was removed (deleted) from a card, this wasn’t correctly adjusting the due date for the card itself.
Similarly, when the last task with a scheduled due date was no longer scheduled, this wasn’t correctly adjusting the due date for the card.
Both bugs have been fixed. They were real edge-cases, so it’s likely that most users never noticed them in the first place, but still…
We have been busy through the holiday season, as usual, but there isn’t a lot of stuff to show you yet since the big new thing we are working on — a more automated and efficient account management and billing system — won’t be ready for a while.
Meanwhile, we have been working through bug fixes on a regular basis; many of them obscure and probably unnoticed by anyone but the Kerika team itself, but we don’t like to have known bugs sitting around so we knock off bugs fairly quickly even if no one has complained (yet).
Here are some of the bug fixes we have done recently (in no particular order):
A problem that affected direct sign up users who wanted to preview their documents, but didn’t allow third-party cookies to be set in their browsers.
An obscure situation where someone who owned a board, but wasn’t part of the board team, shared it with another user: in some situations the second user didn’t see this board listed correctly in their Shared With Me tab of their Home page.
Another obscure circumstance in which a board owner’s face wasn’t shown correctly in the Shared With Me tab of other users.
Helping a user restore access to a board that had gotten corrupted somehow in the database: this wasn’t the user’s fault and we wanted to make sure no work was lost.
Some improvements to labels used in My Preferences to clarify (better) the user’s choices.
Fixing at least one situation where someone wanting to sign up with their Google ID (as a Kerika+Google user) was getting endlessly redirected by Google and never reaching Kerika. (For some reason everyone who reported this problem is located in Norway; don’t know why…)
A problem affecting direct sign up users: they weren’t seeing thumbnails of their files in their Kerika cards and canvases.
Some situations where a browser left running Kerika overnight didn’t refresh itself automatically the next morning, and required the user to manually refresh the view.
Traditionally, in a Kanban or Scrum board the priority is denoted by the position of the card within a column: cards that are higher priority are placed higher within a column, and the card at the top of the column is the highest priority at that stage of the workflow.
For example, in this view of a board the highest priority item for Planning & Design is the card on top of that column:
This method has the advantage of simplicity and clarity: there is no ambiguity about what is the most important work item at any stage of the workflow.
The disadvantage of this method is that as many cards start to move across the board, especially on boards where the workflow is complex (i.e. the board has many columns), it becomes harder to track all the cards that are especially important.
In other words: the simple method doesn’t scale well, and our goal with Kerika is to provide the simplest user interface on top of the most capable work management system, so we realized we needed to do something more.
With our latest version, Kerika makes it easier to explicitly tag each card with a priority of Normal, High or Critical:
Along with assigning tags to a card, you can now set the priority of the card as well: by default all cards are Normal, but they can alternatively be flagged as High Priority or Critical.
Viewing all the High Priority and Critical Cards
We have also extended the Highlights function for Task Boards and Scrum Boards to make it easy to quickly see all the High Priority and Critical cards on a crowded board:
When you are looking at a board, the High Priority and Critical cards are also highlighted with small stars: a solid red star for Critical, and a hollow red star for High Priority:
The Normal Priority cards don’t have any star; we didn’t want to crowd the design which would have made it harder to spot the more important High Priority and Critical cards at a glance.
High Priority and Critical Cards across all your Boards
Previously, when you hid a column Kerika would show that like this:
The name of the column that was being hidden was shown vertically, to make it easier to retain the overall context of the board.
We have improved this so hidden columns now look like this:
The subtle (but important) distinction is that Kerika now shows you how many cards are in the hidden columns, not just the name of the column. We think this will make this feature more useful, to more people, more of the time.
If you are working with Kerika’s unique Whiteboards, you will appreciate a new feature we have added: you can select any existing line or arrow on a canvas and change it to a different style of line or arrow.
We had previously added similar functionality for changing a shape from one form to another, e.g. a rectangle to an ellipse, while preserving all the other properties and content of that shape; now this is possible with lines and arrows as well.