ScrumBoard / Blog: Recent posts

This version contains quite a lot of minor bug fixes. They're mostly related to the filtering functionality(which affects all operations) and searching.

It's the last released version for now(unless I get some bug reports) because I've implemented all of the features I planned to implement. Perhaps in the future I will add some more stuff, please send your feedback to my email address.

A new version has just been uploaded. It contains some new functionality - filtering tasks by their states. You can now use a combo box on the toolbar to show tasks having a particular state. For example you can choose only the ones that are still "TODO" during a daily standup.

Enjoy and please report any bugs to tdolbniak (at) gmail.com

A new version has been released. It contains a lot of stuff, but mainly a change in approach. Here's a list of changes:

• "New DB" function - before adding projects and tasks to the application a new DB has to be created, just like a new document in a text editor or a spreadsheet. Of course an existing DB can be loaded instead.

• Task states definition dialog - a new dialog that can be found in the "Task" menu. It can be used to edit the current chain of states for an existing DB. It also pops up when creating a new DB. There's also a switch in the settings page(DB tab) and if you check it, the dialog will be pre-filled with a standard list of states: "TODO, IN PROGRESS, DONE" when creating a new DB.... read more

Version 1.6 is now released. It contains some minor improvements in the search mechanism, implementation of a simple about dialog and some other stuff I don't remember already :)

Version 1.5 compiled & uploaded.

It contains a major change - possibility of locking DB by a user. This option can be enabled in the settings page.

When opening a DB you will be asked to specify your name. It will be stored in the DB during the time when it's opened. Any other user trying to open it will get a message saying that this file is locked by someone else. They will be asked if they want to open the DB in read-only mode, cancel opening or "force lock". The last option removes the lock created by the firs user and replaces it with a name specified by another one. This can be useful when someone locks the DB and forgets to close it disallowing all the other people to make any changes. This, of course, can be harmful as you're able to remove a lock created by a user actually working on a DB. That's why you should always contact the person who locked the DB originally.... read more

Version 1.4 uploaded. It contains the implementation of "autoserialize" switch which makes the app save the data base after every change you make to any project or task.

Version 1.3 has just been uploaded. It contains an implementation of the settings page. App customization is now easier. See the options in the "settings" menu.

Version 1.2 has been uploaded and is ready to download. It contains some minor improvements related to the searching mechanism.

It is now possible to hide the search bar at the bottom of the app. You can do it by clicking the "X" button on the right or by pressing escape while the search box has focus.

Another new feature is that you can press enter when you're in the search box which works like clicking "next".... read more