For a while now, our Kerika+Box users have had a very nifty feature that allowed them to create a new Box Note from within Kerika itself, and have that note automatically attached to the Task Board or Scrum Board card that they were working on.
(Which meant, naturally, that this new Box Note was also automatically shared with everyone on that particular board’s project team!)
And since this was a very handy integration with Box, we added it to our Whiteboards and canvases as well:
We added this because Google Docs had equivalent functionality: Google enabled us to create a new Google Doc from within a Kerika+Google board and have that new Google Doc attached to the card the user was working on.
The trouble was, Box’s Content API didn’t really have an official way of doing this, so we came up with a workaround that worked fine for the longest time — so long, in fact, that we forgot that it was even ever implemented as a workaround…
Unfortunately, that broke a few days ago. Box did an update to their platform that stopped our workaround from working any more, which means that, at least for now, we will have to stop offering this feature for our Kerika+Box users.
Hopefully we will be able to get Box to give us official support for this feature, so Kerika+Box remains at least as good as Kerika+Google
We have created a new tutorial video on how Notifications work in Kerika. It is based upon our new user interface, which hasn’t been released yet, so some of the menu options shown on the top-right of Kerika boards will look a little unfamiliar
We are sometimes asked how people can move projects from one account to another, either because someone has left their organization, or simply because they want to consolidate ownership of all project assets within a single account owner.
We plan to make this process simpler in the future, but for now here is a simple workaround that can help you achieve the end-goal.
Step 1: Add User B to User A’s project as a Team Member.
This is the simplest option: once User B has been added as a Team Member on User A’s project, she can then copy and paste the entire project over from User A’s account into her own.
Step 2: Copy User A’s Project
Normally, your Home Page shows a consolidated list of all the projects you are working on, regardless of who owns them.
But, you can filter your view of the Home Page to just show those projects owned by a certain user, like this:
Using this filtering option can make it easier to find just those projects that are owned by a particular user, like this:
Now, User B can select one of User A’s project (that she has access to), and do a Copy using the Copy button that appears at the top of the list of projects:
Step 3: Paste the Project
Once User B has copied the project into her Kerika Clipboard (which, by the way, exists on the server and not on her browser itself, so you don’t have to worry about your browser crashing in the middle of this operation), a Paste button will appear when she then returns to view her own account:
Step 4: Get rid of the old Project
Once the Paste operation has finished (it can take a minute or two, depending upon how big the board is that that is being copied and pasted, and in particular how many files are attached to that board), it would be a good idea for User A to get rid of her original project, so that there is no longer any confusion about which version is the active one.
Deleting a project is simple: just select something that you own, and you will see a “Move to Trash” button appear at the top of the list of projects:
(Since Kerika offers a Trash/Recycle Bin feature, deleting is actually a “move to Trash” operation: if you delete a project by mistake, you can always restore it from your Home Page’s Trash.)
By default, the new canvas is simply called “Canvas”, but like with any other attachments on a card, you can easily rename it by clicking on the pencil icon that appears to the right when you hover your mouse over it:
Clicking on the “x” button at the far end will let you delete a canvas that you no longer need:
If the canvas is empty — which means that there is nothing visible on the canvas, and nothing in the canvas’ Trash either — you see a simple confirmation message asking if you are sure you want to delete it:
But, if the canvas is not empty, you see a Restore option instead:
If it seems puzzling why a canvas that appears empty isn’t really empty, make sure you open the canvas and take a look at the Trash: there may be items there that you had previously removed from the canvas:
In this example, above, the canvas looks empty but isn’t really: there are items in the Trash.
In situations like this, Kerika is careful to avoid losing all your work: until you empty the Trash on a canvas, the canvas isn’t considered to be truly empty, and until a canvas is truly empty, it cannot be removed from a card.
So, in this example, you see the Restore option rather than the Delete option:
Kerika makes it very easy for everyone within a distributed team to always have the same clear understanding of what’s most important, within any part of a project’s workflow.
With a Task Board or Scrum Board, simply drag cards up or down to show their relative importance: stuff that is on top of a column is more important than stuff that’s at the bottom.
This is a super-simple way of signaling priorities: it removes all ambiguity within a distributed team, because only one card can be at the very top of a column — i.e. only one item can be “highest priority” — and only one item can be in the second position within a column — i.e. only one item can be “next highest priority” — and so forth.
A great side benefit of this method is that it keeps managers honest: it is no longer possible for a point-haired boss to claim that a bunch of things are all “top priority”.
Michael DeAngelo, Deputy CIO for Washington State and long-time Kerika user, will be speaking on “Lean Government” in Kirkland on June 24: how the Office of the CIO has been pioneering the adoption of Kanban, Scrum and “holocracy” within the state. Check it out at http://www.meetup.com/BeyondAgile/events/222991832/
Kerika is work management for distributed Lean and Agile teams