Skip to content

Get More Done, With Kerika

Task Management for Remote and Distributed Teams

  • KERIKA.COM
  • FEATURES
  • USERS
  • PRICING
  • ABOUT US

Automatic version tracking

April 23, 2016Agile & Scrum, Kanban & Lean, Team Collaboration, Technology, UsabilityBox, Direct Sign Up, Document Management, Google Apps, Kanban, Kerika, Scrum, Task Board, Whiteboarduser

Another great new feature: if you upload a file on any card, canvas or board with the same name as a file that’s already attached to that particular card, canvas or board, Kerika will automatically keep track of these as being different versions of the same file.  This makes it even easier to organize all your Kerika project files.

Here’s how it works:

Kerika lets you add files to any cards, boards or canvases, on any of your Kerika Task Boards, Scrum Boards or Whiteboards.

There’s no limit to the number of files you add, nor any limit on the size of these files.

When you add a file, to a card, board or canvas, Kerika automatically uploads that file and shares that with everyone who is part of your board’s team. You don’t have to do anything: Kerika makes sure that all the Team Members have read+write permission, and all the Visitors have read-only permission.

These files are stored in your Google Drive, if you are using Kerika+Google, or in your Box account, if you are using Kerika+Box, or with Kerika if you have signed up directly with an email address.

That’s how Kerika has always worked; what we have added is an automatic versioning feature that checks when you add a new file to see if has the same name, and type, as a file that’s already attached to that particular card, canvas or board.

If the file name and file type match something that you have already added, Kerika automatically treats that new file as a new version of the old file, rather than as a completely different file. This makes it really easy to manage your Kerika project files.

Here’s an example: this card has a file attached to it called “Foo.docx”.

File attached to a card
File attached to a card

If a Team Member adds another file to this same card, also called “Foo.docx”, Kerika will treat that new file as a different version of the same Foo.docx, rather than as a completely different file:

Uploading a new version
Uploading a new version

Accessing these older versions is easy: if your Kerika files are in being stored in your Google Drive, you can get the older versions using the Google Docs File menu:

Google revision history
Google revision history

If your files are being stored in your Box account, you can access the older versions from the menu on the right side of Box’s preview window:

Box version history
Box version history

If you signed up directly with Kerika, you can access the older versions from within Kerika’s file preview:

File preview
File preview

Clicking on the Older versions of this file link on the top right of this preview will give you a list of all the old versions of this file that Kerika has:

Older versions
Older versions

So, that’s it: simple, easy, automatic tracking of multiple versions of your project files! Brought to you by Kerika, of course.

 

Post navigation

← Calendar syncing Apologies for the long absence… →

Archives

  • May 2025
  • April 2025
  • January 2025
  • November 2024
  • October 2024
  • August 2024
  • June 2024
  • May 2024
  • April 2024
  • March 2024
  • February 2024
  • January 2024
  • December 2023
  • November 2023
  • October 2023
  • September 2023
  • August 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • July 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • October 2021
  • August 2021
  • May 2021
  • March 2021
  • February 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • July 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • December 2019
  • November 2019
  • October 2019
  • September 2019
  • August 2019
  • July 2019
  • June 2019
  • May 2019
  • April 2019
  • February 2019
  • January 2019
  • December 2018
  • November 2018
  • October 2018
  • September 2018
  • August 2018
  • July 2018
  • June 2018
  • May 2018
  • March 2018
  • February 2018
  • January 2018
  • December 2017
  • November 2017
  • October 2017
  • September 2017
  • August 2017
  • July 2017
  • June 2017
  • May 2017
  • January 2017
  • November 2016
  • October 2016
  • September 2016
  • August 2016
  • April 2016
  • March 2016
  • February 2016
  • January 2016
  • December 2015
  • November 2015
  • October 2015
  • September 2015
  • August 2015
  • July 2015
  • June 2015
  • May 2015
  • April 2015
  • March 2015
  • February 2015
  • January 2015
  • December 2014
  • November 2014
  • October 2014
  • September 2014
  • August 2014
  • July 2014
  • June 2014
  • May 2014
  • April 2014
  • March 2014
  • February 2014
  • January 2014
  • December 2013
  • November 2013
  • October 2013
  • September 2013
  • August 2013
  • July 2013
  • June 2013
  • May 2013
  • April 2013
  • March 2013
  • February 2013
  • January 2013
  • December 2012
  • November 2012
  • September 2012
  • June 2012
  • May 2012
  • March 2012
  • February 2012
  • January 2012
  • December 2011
  • October 2011
  • September 2011
  • June 2011
  • May 2011
  • April 2011
  • March 2011

Categories

  • Academic & Nonprofit
  • Agile & Scrum
  • Best Practices
  • Bug Fixes
  • Ephemera
  • Global
  • Government
  • Intellectual Property
  • Kanban & Lean
  • Kerika
  • Technology
  • Tutorials
  • Uncategorized
  • Usability
  • Whiteboards

Recent Posts

  • How to Build an Effective Help Desk Workflow: A Step-by-Step Guide
  • Kerika is rated by Top Business Software
  • Archived vs Active Boards: Simplify Your Workspace
  • Kerika is again Sourceforge’s Category Leader
  • How to Build a Winning Business Model: A Step-by-Step Guide

Recent Comments

  1. Anonymous on Making it easier to know when Kerika has a new version
  2. Security within a Virtual Private Network | Kerika's Blog: Get on the same page! on Heartbleed: no heartache, but it did prompt a complete security review
  3. Security within a Virtual Private Network | Kerika's Blog: Get on the same page! on Heartbleed: no heartache, but it did prompt a complete security review
  4. What we did in 2014 | Kerika's Blog: Get on the same page! on Dropping the “Render Server” feature
  5. Why we are integrating with Box; Part 8: Our experience with Box (so far) | Kerika's Blog: Get on the same page! on Why we are integrating with Box; Part 7: Disentangling from Google
Privacy Policy Proudly powered by WordPress