For these folks, here’s a quick tutorial video that shows you how your files are stored and shared.
OK, another tutorial video done: this time on how to use Kerika with Box.
Kerika works seamlessly with Box for secure storage of all your project files: just sign up as a Kerika user with your Box ID, and all your Kerika files will be stored in your own Box Account, where they will always be under your control.
This tutorial video shows you how.
Intended audience for this video: new Kerika users who want to leverage Box.
We have made a change to the Card and Board Attachments feature to prevent users from changing the extension of a file they have already added: for example, a “.xlsx” file can’t be renamed as a “.docx” file.
We did this because changing the file type often had unpredictable consequences when a Team Member tried to upload an attachment.
This restriction applies to the most common file types, not all. Here’s how it works:
In the example above, an image has been added as an attachment to this card, and it has the .PNG file type/extension.
When you hover your mouse over any attachment, Kerika will show you the actions that are possible with that attachment, one of them being Rename.
If you select Rename, Kerika will make sure you only change the file name, not the file type/extension (.PNG in this example):
If you are using Kerika with Google, you don’t have to convert your documents to the Google Docs format in order to use Google Drive.
You can use this preference setting to ensure that your Microsoft Office documents, for example, are retained in MS Office format even while they they are stored and shared using Google Drive.
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.
Here’s an example:
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.
Team Drives is available on G Suite Enterprise, G Suite Business, or G Suite for Education editions.
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.
(This was inspired by our recent fix to a bug that didn’t properly download the latest version of a file attached to a card or canvas; while fixing this we started thinking deeper about how to make file management even easier for our users.)
Here’s how file management works now: when you hover your mouse over a file attachment, a new action called +NEW VERSION is available:
Clicking on the +NEW VERSION button will let you pick any file from your computer that’s of the same type, and Kerika will add that and track the file as a new version of your old attachment.
This is possible even if the new file has a different name altogether, as long as the two files are of the same type.
For example, a filed called Budget.xlsx can get a new version that’s called Plans.xlsx — both are tracked as different versions of the same file, even though they had different names.
This makes it even easier to manage all your files using Kerika!
Thanks to our users at Oxbow Farm, we have found and fixed a bug that affected users who signed up directly with Kerika: clicking on an attachment in the card details was downloading the original version of a file, not the latest.
Here’s what was happening: when you add a file to a card or canvas, Kerika checks to see if that file was already being used on that particular card or canvas. If so, Kerika automatically handles your latest upload as providing a new version of the old file, so you see just one entry in your card attachments view:
The bug that we recently discovered, and fixed, resulted in Kerika downloading the original version of the file when you used the download option that appears after you select an attachment from the list of attachments on a card.
If you clicked on the attachment’s thumbnail to open a preview of the file, Kerika was correctly opening the latest version of the file. The bug was only in the download action, and that’s been taken care of now.
We have a new (five-minute) video that gives a fast overview of Kerika’s many capabilities:
Let us know what you think!