We found and fixed a bug that was kind of annoying, even if it affected only a small handful of users: if you transferred ownership of a board to someone else, that board wasn’t appearing correctly in the Shared With Me tab of your Home page.
We found and fixed a bug recently that was stopping Account Owners from inviting people to join a board team, unless the Account Owner herself had a specific role in the team (i.e. was a Board Admin or Team Member).
This isn’t how it is supposed to work: Account Owners have all rights to all boards that are owned by their accounts, which means they can change the board team on any board they own.
This gave our users more choices in terms of how they signed up for Kerika, and which cloud service they used to store their project files, but we continued to resist offering a direct sign up mechanism:
We remained convinced that third-party signup and login, using OAuth, would dominate user preferences — under the theory that no one really wanted to remember yet another password for yet another web service.
Our technical architecture also restricted us from offering a direct sign up choice because we had tied together the issues of authentication and file storage: it was how our original integration with Google had been done, and we had simply duplicated that model when we added Kerika+Box.
This changed in 2015, when Box announced the Box Platform as a new service — although originally it was called the “Box Developer Edition” when it was unveiled at the BoxDev conference in April 2015.
Kerika was probably the first task management app to sign up to use the Box Platform; in fact, we were in the very first batch of beta users for the service.
This new integration with Box allowed us to finally offer a direct sign up mechanism for new users:
Now, you can sign up with any email address: it could be a company email, a Yahoo email, a Microsoft Live email… even a Gmail address.
When you sign up directly with Kerika, we use the Box Platform to securely store your project files:
We create an account at Box that’s dedicated to storing your Kerika files.
We do this automatically and behind the scenes: you might never know that your files are actually being stored at Box, rather than on a Kerika-operated server.
While this seamless integration is great from a user experience perspective, it doesn’t mean that we want to hide our Box links: in fact, we would actually like to boast about our use of the Box platform because Box is so well regarded for the robustness, security and privacy of their cloud storage service.
So, now you know where your files are stored when you sign up directly as a Kerika user: inside the Box Platform!
It turned out we had an internal problem with routing requests for such accounts, when they were made from within the Kerika app itself, as a results of which we must have seemed very unresponsive to some folks who never heard back from us. Our apologies for this!
Anyway, if you would like to get a free Academic & Nonprofit Account, which lets you have an account team size of up to 10 people, please let us know by emailing firstname.lastname@example.org. That might be the most reliable way of getting in touch with us…
A new tutorial video that shows you how you can customize the layout of any Task Board and Scrum Board, and — more importantly — switch any board from being a Task Board to being a Scrum Board, or back.
Only Kerika lets you have several Backlogs within the same Account, and easily pull cards from different Backlogs into the same Scrum Board if you want to combine work items from several Backlogs into the same Sprint.
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.)
When we first built Kerika, we emphasized privacy strongly — too strongly, in retrospect, particularly for our enterprise users: Kerika made it too hard for your colleagues to discover your work, since they could know about a board only if you had added them to the board’s team.
With our newest update to Kerika, we are addressing that concern: you can now make projects viewable by your Account Team.
If you set a project’s privacy to be “Viewable by the Account Team”, anyone who is part of your account team — i.e. all the folks that are currently working as Team Members on all the projects owned by your account — can discover it.
Next up: we are upgrading our Google Apps Marketplace integration to also use OAuth 2.0, so that all logins to Kerika will be with OAuth 2.0, across all platforms.
The background to this work is slightly wonky, and reflects the way Google Apps Marketplace has evolved within the Google ecosystem.
If you sign up for Kerika+Google today, you actually go through a OAuth 2.0 authentication and authorization process with Google, which gives us your basic profile information (name, email, photo) that we use to set up your Kerika+Google account, as well as access to your Google Docs.
Google has deprecated OAuth 1.0, so we are updating our Google Apps Markeplace to also work with OAuth 2.0, just like a regular sign-up through Kerika.com.
This change will not affect any existing users: the most visible effect will be on our Sign Up page, which will start to show three options for new users:
Sign up for a Kerika+Box account: this will work as it does today – it will use OAuth 2.0 to set up a Kerika account using your Box credentials (name, email address, and access to your Box account to store your Kerika-related files).
Sign up for a Kerika+Google account: this will also work as it does today – it will use OAuth 2.0 to set up a Kerika account using your regular Google credentials (e.g. Gmail ID, YouTube ID) and store your Kerika-related files in your Google Drive.
We have a growing community of users in various agencies within Washington State government, and we are happy to provide the essential project management and team collaboration tool needed to achieve the Governor’s mandate for “Lean Government”.
Among other agencies, we are proud to serve people in:
To help folks within Washington State agencies understand how (and when and why…) they should Kerika, we have partnered with the state’s Office of the CIO to produce a quick guide to Using Kerika for State Government Work: