• sto241 Moving Stories between Projects
• sto242 Create issue from task

Moving Stories between Projects allows the Product Owner to push a Story to another project. If he is the Product Owner of the target project, the Story will be moved to its Product Backlog. Otherwise, an Issue in the target project will be created. Please note that moving a Story will not keep its changelog and comments.

Create Issues from Tasks allows the Product Owner to easily transfer a Task to the Issue inbox. This allows accepting a Story with defects and directly create the corresponding Issue for further processing.

Thanks to the Congstar Hackathon team for code contributions.

Fixed bugs

• iss1145 OpenID login fails with version 0.25
• iss1144 Searching crashes
• iss1147 EntityDoesNotExistException in user login
• iss1140 System Message date: Info and error message
• iss1142 allow "+" in email address
• iss1143 Project admin setting was unset and cannot be set again
• iss1146 Error when uploading file with unicode characters in the file name
• iss1159 Planing Poker reveals cardvalue before clicking "show"
• iss1172 Meta: G+ and FB like on the main page are broken
• iss1134 Convert Bug->Story, bug appears fixed in Release

New Features

• sto221 The Richtext-Editor will now prepend itemization/enumeration when text is selected (instead of overwriting the selected text)
• sto231 Blog entries will have their date created on publication (not on entity creation); explicit dates can still be set
• sto239 If Qualities are cross-referenced in Stories, a Task for each Quality will be automatically created when pulling Stories to a Sprint
• sto232 Planning Poker estimation help will now continue working after cards are revealed
• sto235 The average velocity will now be calculated using a moving average (of the last three Sprints)

Fixed Bugs

• iss1037 Fixed "Move to Inbox" (Issues) not working
• iss1104 Fixed Unexpected Error using Undo on Task creation
• iss1100 Unclaiming an Issue will now create Journal entries
• iss1041 Completed Stories will not continue to be exported to the homepage
• iss1091 Fixed Exception on other client when new User is added to project
• iss1081 Fixed references to files not working
• iss925 Fixed Whiteboard deformation for Stories with high estimation
• iss1021 Fixed submenus on the navigation appearing as small lines
• iss1038 Fixed crash when adding image file links in comments
• iss767 Completed Tasks will not be removed when kicking a Story from the Sprint
• iss477 Fixed non-expanding/non-collapsing blocks after executing certain menu actions
• iss1087 Stories that were rejected in past Sprints can now be deleted
• iss1070 Removed wrong tooltip from Stories
• iss1024 Fixed incorrect adjustment of remaining hours when repeatedly clicking "-" on burned hours
• iss1109 The Sprint Backlog PDF now contains the Sprint goal

We have also moved our binaries from SourceForge to our own server, since SourceForge has decided to urge developers to include adware into their releases. This could result in slower downloads, but you will not have to live with drive-by downloads.

Happy scrumming!

Fixed Issues

• iss1081 References to files don't work
• iss1037 "move to inbox" (issues) doesn't work
• iss1041 Export stories from sprint history to homepage
• iss1038 Image links in comments cause Kunagi to break
• iss1024 Remaining hours over Burned Hours
• iss477 Non-expanding/non-collapsing blocks
• iss1070 Hide Mouse Over on Product Backlog items

Happy scrumming!

Fixed Issues

• iss972 After a Bug is closed, it will continue to show the severity. Reopening a Bug puts it into Bugs, not the Inbox.
• iss790, iss948 Once loaded, the Whiteboard now should perform better and create less CPU usage when using many Stories and Tasks.
• iss300 We included some font support for Asian characters although we cannot really test whether it did the trick.
• iss895 "Show Details" now should work everywhere.
• iss559 The Wiki was redesigned to be more in line with Kunagi's overall UI concept. Thus, features that were hard-to-find or not working before, should now be available in the Wiki.
• iss885 The ideal burndown line now will remain in its original position if the Sprint is lengthened.
• iss966 Fixed a crash when a user would start entering a Comment, but then navigate away instead.
• iss975 Fixed a crash that could occur when creating Releases.
• iss899 Fixed crashes that could occur when searching.
• iss229 Included some missing tooltips.
• iss902 Hovering drag handles of Stories in the Whiteboard will no longer display a cursor to suggest that they can be moved.
• iss754 Uncertain projection (i.e. projection that is based on values marked for re-estimation) will now be displayed in grey in the Product Backlog.
• iss553 When a Sprint is lenghtened, the start date of the next Sprint will be automatically adjusted acoordingly.
• iss997 Fixed a bug where searching would not work after switching projects.

Meanwhile, we have a bugfix release for you fixing some weirdnesses that slipped into 0.24. Make sure to check it out. Here's what we fixed:

• iss921, iss929 Clicking links in editable fields would trigger edit, leading to data loss in some cases
• iss947 Internal application data backups are now properly deleted
• iss954 fixed crashes when Kunagi tried to send a notification e-mail but couldn't

For Admins, we have an admin view that displays system, service and environment information and log messages. Also, there are functions for backup and safe shutdown.

For other Users, we have some minor UI improvements and several bugfixes. We also worked on our code quality and expect less Exceptions to be thrown that force users to restart the interface.

Lastly, we sat down and made Kunagi work in Internet Explorer 9. As a side effect, it might even work in IE8 now.

Get the new version while it's hot! Here's the complete list of changes:

New Features

• sto202 Story progress is now visualized in the Whiteboard
• sto204 Create Story button at the bottom of the PB
• sto230 Admins have a admin page now, where they can view system information, logs and access a backup and shutdown feature
• sto220 Users that post Issues to us or subscribe to existing Issues on kunagi.org are now automatically notified about changes
• sto210 The Personal Preferences page now allows users to sign up for e-mail notification on Kunagi events
• sto191 Team Velocity at the top of the PB is now displayed graphically as a sparkline chart

Fixed Bugs

• iss824 FIles that contain a # (and potentially, other "invalid" characters) can now be correctly downloaded from the File Repository
• iss764 Translated a session logout message that was in German
• iss769 Cannot open Whiteboard after creating Impediment from Task
• iss779 Fixed Unexpected Error after switching Sprint
• iss792 Fixed a bug where an admin user could change his own password without entering his current password
• iss753 Bade the difference between H1 and H2 in Wiki more distinct
• iss830 Fixed "null" appearing when Kunagi appends text to an empty Statement
• iss632 Added missing infos in PDF report for Bugs
• iss804 Fixed Search throwing an EntityDoesNotExistException
• iss702 Kunagi should now work with IE9

Make sure to get it while it's hot.

Important notice to all upgraders!

We have changed how Kunagi finds its data to make configuration easier in the future. If you didn't customize the data path or configuration path, nothing changes for you. In some cases, after upgrading Kunagi, it will use a different data directory and all your projects will be "gone" (they are, in fact, still there). In this case take a look into your log file to see which data path is used by Kunagi. Then stop Kunagi, delete this data path and move your old data directory to this path. Please don't accidentally delete your real data directory, create backups before deleting anything! Start Kunagi and watch for warnings in the log file. More infos on data path configuration in the FAQ.

Back to new features...

New Features

First off, we have finished the long awaited cemetery for Stories (sto187), Tasks and Comments that were not available in the UI after their respective Sprints have been completed. It replaces the (formerly purely textual) Sprint History.

In the process of working on the Sprint we have changed the way text input works: Contents are now auto-saved as you type. The buttons "Apply" and "Cancel" have thus gave way to one button "Finish".

Also, there is also a huge list of fixed Issues, including some really great stuff. Here's the complete list:

Fixed Bugs

• iss716 Creating Story from Issue no longer drops its Themes
• iss720 Stories that contain blocked Tasks not show the blocked icon
• iss727 Stories may not have an estimation value of 0
• iss709 Themes that are currently unused are hidden from the Themes widget
• iss738 When accepting Issues as Ideas, the UI no longer auto jumps
• iss740 A unintended bogus change log entry on Story rejection has been removed
• iss726 "Keep me logged in" on the login screen is now auto-checked
• iss729 References in the Journal are now links that lead to the referenced entities
• iss717 The dashboard now not only shows the Team's, but also the Product Owner's upcoming work
• iss700 To avoid confusion, Stories without Tasks are no longer displayed as "completed", but as "no tasks"
• iss620 National-specific characters (like Kanji etc.) should no longer disappear from texts
• iss719 Some weird behaviour when kicking from / pulling Stories to / form Sprints was fixed
• iss724 Kunagi now hides Tasks that have been carried over from past Sprints, but have already been completed to avoid confusion about Sprint progress (those Tasks can still be seen in the Sprint History; see sto187)
• iss721 Missing "Unclaim" for Tasks should now be there
• iss706 Removing completed Stories from Sprint no longer makes them disappear altogether, they are 'uncompleted' instead
• iss722 The same day in the calendar no longer appears as several dates in certain cases
• iss728 The Communication Indicated (in the top left, next to the Kunagi logo) now turns red if the server fails to respond and displays the server response time in its tooltip
• iss549 Fixed race conditions when the Product Owner sorts the Backlog while other Users expand and collapse Stories
• iss763 Fixed a bug where claimed and fixed messages for Issues in the Journal would appear in wrong order
• iss760 0 SP Stories no longer appear in the Planning Poker estimation help
• iss750 The keyword to generate a table of contents in the Wiki is now __TOC__ instead of TOC (in line with Wikipedia)
• iss747 Bugs are not directly convertable to Ideas (instead of having to move them to the Inbox first)
• iss751 Fixed a bug where inline code would appear as a block when placed at the beginning of a line
• iss691 Fixed blocked Tasks missing from the PDF Sprint Report
• iss739 Selecting "Show change history" on collapsed entities now properly expands them and shows the Change log
• iss749 Entity references that appear with brackets or colons are now recognized and displayed as links correctly

Stay tuned for more soon!

Here is the full list:

• iss628 fixed Typos
• iss630 Unclaimed Tasks can no longer be unclaimed
• iss561 Offline users were sometimes shown as "idle"
• iss590 Exception in Demo using OpenID
• iss660 EDNEException on Google-ID Login
• iss644 Blank screen on login (LDAP email)
• iss617 EntityNotFound after deleting new Impediment
• iss613 Completed Issues are now written into the Release notes on Sprint switching (will be changed again in the near future)
• iss653 Invalid LDAP login produces new users
• iss659 Missing font for chart

The Release view now has a field that holds a checklist for releasing (sto197) new versions. We have also reworked how tooltips within the program work (sto194), but that should be less important for the everyday work.

As always, there is a (this time quite long) list of issues that have been fixed. Here is a complete list:

Fixed Issues

• iss375 Resetting passwords did not work
• iss568 Impediments can now be reopened (the action is reported in the Journal)
• iss604 Tooltips sometimes didn't hide
• iss562 Password login problem
• iss557 The Whiteboard was sometimes confused about Task order. Only Todo-Tasks can now be ordered manually, the rest is done automatically.
• iss546 After dragging entities, the collapsed/expanded state is now preserved correctly
• iss537 Product Backlog estimation projection should now work correctly (again)
• iss598 Users cannot be deleted anymore, because this leads to data problems; they can, however, be disabled
• iss525 Kunagi could crash when using the navigation while an editor is open
• iss587 fixed random Exception when opening Product Backlog
• iss596 Kunagi now works out of the box with Jetty
• iss473 fixed a bug where creating a user would fail on Websphere
• iss580 Entities in PDFs are now sorted correctly
• iss583 Kicked Stories now go to the top on the Product Backlog when kicked from a Sprint
• iss575 users can now be configures in the project administration view
• iss565 Numeric input via Numblock did not work

The packages are not exactly what you would call a in-program feature. There are, however, also several fixes of recent bugs and a couple of UI improvements, so this version is definitely worth your while.

Here we go with a complete list of what is new:

Completed Stories

• sto184 Package for Ubuntu: Kunagi is now available as a deb package
• sto156 Package for Windows: Kunagi is now available as an exe installer
• sto172 no more useless JavaScript stack traces when errors arise

Fixed Bugs

• iss544 Tomcat used to try and persist Kunagi sessions although this is not possible
• iss472 Stories are now marked completed when there are no Tasks left (the Product Owner still has to review and accept/reject them)
• iss529 there is now no more "Publish" button, when there is no homepage
• iss540 in the Planning Poker screen, "Show votes" and "Reset" used the same spot, leading to misclicks when several users tried to moderate the session
• iss545 Users can now configure a name for their Kunagi installation that appears in the browser's title bar
• iss550 RSS feed now have unique ids, putting an end to confused feed readers
• iss527 expanding a user block now shows the person's real name
• iss533 renamed task "close" to "done"
• iss397 SMTP port configuration now works correctly
• iss526 after several failed pings, the Kunagi UI will now halt to prevent data loss
• iss528 It is now possible to remove OpenIDs
• iss539 the burndown chart now handles deleted Tasks correctly
• iss547 the burndown chart now handles Stories that are removed from Sprints correctly
• iss548 Tasks are now corretly cleared when kicking Stories from Sprints

Completed Stories

• sto181 Wiki links now indicate article existence
• sto183 The current Sprint info is now rendered in the Next Sprint view

Fixed Issues

• iss487 Fixed some navigation errors
• iss494, iss490 Fixed some crashes

First of all, Kunagi 0.18 introduces reasonable support for Chrome and Opera. Using Kunagi with Opera before was far from productive, but is about fine now.

There is also one more feature for the Product Backlog: Splitting Stories allows the Product Owner to, well, split Stories. The advantage is that the change history logs that event and the relationship of the Stories is maintained by an automatically introduced common Theme.

There is also one little change for Releases. You may specify a Release Script in the Project Administration view that will be executed when you publish a Release.

And as always, here is the list of bugs and issues fixed with the new release. I'd like to point out one especially exciting fix, however:

You can now use the mouse wheel to scroll the view while dragging (iss151).

Fixed Bugs

• iss437 Forward/Back navigation was broken
• iss465 Project Events including Qualities lacked a link to the Quality
• iss470 Fixed a bug in Ilarkesto libraries
• iss391 There is now a PDF-Download for Quality Backlog, Issues and Releases
• iss478 Generate PDF would crash for some Wiki pages
• iss457 It was possible to kill the program by dragging Stories aroung in the Whiteboard
• iss449 Qualities are now ordered alphabetically in the Product Backlog filter
• iss469 Fixed crash when creating a new Story in a filtered Product Backlog
• iss300 There is now support for some foreign characters in PDF (Turkish and Polish should work now)
• iss443 the Velocity projection in the Product Backlog failed for some pages

Kunagi now runs with the new GWT version 2.2.

• sto165 There is now a brand new way to create Stories. In the upper right corner of the Product Backlog, Stories can now be dragged into existence, partly resolving the problem that new Stories are always created at the bottom.
• sto166 We have now a filter for the Product Backlog. Even sorting works in the filtered backlog (with one limitation though, that we will fix another time).
• sto169 Kunagi now warns you if you want to end Sprints that have finished Stories that are not yet reviewed.

We also made some changes to the website:

• sto171, sto167, sto149 The website now has a sidebar, a constributor list and an FAQ.

And, as always, here is a list of issues that have been solved in this Sprint:

Fixed Issues

• iss413 there were cases of Exception being thrown on shutting down the application
• iss372, iss430 the website's response to submitting feedback was parsed incorrectly by some browsers
• iss376 Kunagi now won't crash if pinging the server fails
• iss378 Themes are now displayed in alphabetic order
• iss424 Qualities are not displayed in alphabetic order
• iss429 new Issues submitted from the internet are now instantly displayed in Kunagi
• iss408 new Calender events now appear without page reload
• iss410 Participants without roles can no longer edit project properties
• iss388 file names with spaces are now handled correctly by the File Repository
• iss366 Length computation of sprints was incorrect in some cases
• iss381 the Wiki now correctly renders nested lists
• iss394 the maximum file upload size is not limited any more
• iss397 SMTP port configuration should now work
• iss383 the user documentation of Risks prioritization is now correct
• iss357 Users do no longer appear twice in participant lists
• iss398 new Users are now instantly visible in participant lists (without re-login)
• iss401 the log.txt file is now deleted from time to time to prevent excessive file sizes
• iss399 after account creates, a blank page was displayed

Here is the list of fixed issues:

• iss362 Exceptions with Kunagi 0.16 / after upgrade to 0.16 with Tomcat 5.5 and 7
• iss377 Release publishing should not be possible for guests
• iss346 Time effort for Sprint now appears in Sprint Report
• iss375 Resetting passwords should now work correctly

Here are the Stories that were completed:

• sto151 Tasks can now be created by a Create-Task button right in the Task list (no need to open the Story action menu)
• sto155 The Sprint Report has been extended to include more information on completed Stories and Tasks
• sto157 There is now a possibility to configure "free days" in the Project administration. Free days are not taken into account, when calculating burndown projections
• sto152 The change history now opens in shortened form with the option to expand certain event details (leading to a performance boost)
• sto153 Stories and Issues can now be tagged with Themes; Theme-related stories are then displayed in the Story/Issue details
• sto158 Thanks to Olivier Weinstoerffer's code contribution, we now have LDAP support for authentication

There are also a lot of bugfixes:

• iss340 JFreeChart: NoClassDefFoundError
• iss341 Registration possible in spite of disabled registration
• iss321 Setting the data directory is now possible by setting data.path=/my/data/path in the config.properties
• iss294 Exception on changing duration of Next Sprint
• iss334 Crash when editing comments
• iss319 Spelling
• iss284 Another Sprint Burndown Chart Bug
• iss335 Comments from Homepage are Wiki-Syntax
• iss337 Exception when adding Sprints to Releases
• iss338 Blocks without a title cannot be expanded
• iss349 Velocity fails when editing Entities
• iss324 Anonymous submitting issues displays "null" as the issuer's name

During the rest of the month, we are very likely to be caught up in Christmas vacations, so don't expect much, but we will be back in January with the next release, that will hopefully finally include reasonable Browser support and the long promised Tutorial.

There are two big things we aim to accomplish this Sprint: Support for Browsers other than Firefox and a Tutorial to get users started using Kunagi (and get their projects done with Scrum). We will also implement a couple of features that have been requested by users during the last couple of months.

On the side, we have planned a reworked website, because the current one has grown over time (any you can see it). There are also slight plans to rework Kunagi's GUI soon(TM) as well to look more coherent and less chunky, but that's actually not more than a vague idea yet.

So stay tuned for the next Release which is due around December 12th.

We have also reworked the user list to be way cooler than before. For example, it now displays what people are viewing and whether they are idle.

Additionally, we now support

• new version notification
• an ?-card in planning poker
• a little bit of syntax highlighting for editors and start-from numbers for lists
• page flipping for comments (if there are many)

There is also a couple fixes for existing bugs and other kinds of issues:

• iss141 the viewport in textareas used to scroll up when using the toolbar
• iss282 it is now possible to disable Open ID for login
• iss312 the passwords on the admin configuration page are now ****ed.
• iss296 the dashboard was sometimes displaying Stories that were not in the Sprint
• iss313 when using the user management, the system could crash

See below for a more or less full list of changes.

New Features

• sto106 The Wiki syntax for lists now supports sublists
• sto130 Users can now register and log in using OpenID
• sto131 We have now released Kunagi in a way that allows everybody to contribute. See the Developers' Documentation for that
• sto129 Changes to text are now saved automatically and can be restored when the program crashes
• sto79 The Change Log for Entities now shows human readable diffs
• sto111, sto113 Creation of Stories from Issues now crates one conversion event, carries Issue info over to the new Story and sets bidirectional references to link Story and Issue
• sto128 Multiple successive changes to text are now merged to one change in the Change Log
• sto108 Users can now sort Tasks in Stories
• sto133 Developers can now reply by e-mail to Issues submitted from the Internet
• sto115 On the Kunagi website, users can discuss published Entities, like Issues
• sto124 The login form now allows users to stay logged in
• sto122 The current program version is now displayed
• sto134 Bugs now automatically set the current Release as affected when accepted, and the next Release as Fix Release when claimed
• sto126 Label length has been limited to 110 characters in order to preserve UI
• sto125 Developers can now set Tasks as blocked by Impediments
• sto127 Sprint duration can now be set by end date or by duration
• sto123 Entity fields have been renamed to better represent their purpose

Fixed Bugs

• iss264 The Sprint Burndown Chart is now rendered, even if the start date lies in the future
• iss165 Chat content is now preserved for the whole session (and not cleared after some time)
• iss219 Project description fields are now Product descriptions have been renamed, a Vision has been included as a Project description
• iss255 Relative redirects should now work correctly
• iss242 A bug including the creation of Tasks led to a UI lockup and cannot be reproduced any more
• iss271 UI Response Time has been improved
• iss221 enumeration syntax within code blocks in the Wiki is now correctly interpreted as code
• iss213 broken File upload has been fixed
• iss250 Story order in Product Backlog Report is now correct
• iss258 The e-mail validated rejected some correct emails; this issue should be fixed now

• now there is in-program documentation describing all views and fields in Kunagi,
• the login view has been reworked to support correct enter-behaviour and browser autofill features,
• projects can now be switched without returning to the project view,
• you can now set the location that Kunagi saves data to.

Behind the scenes, we have set up a testing framework for code and GUI that should prevent some dumb errors making it into future program versions.

There is also a number of fixes for existing issues:

• iss218 usernames were not required to be unique although the program demands it
• iss225 registration of new users can now be disabled
• iss209 dates could appear cluttered for long Sprints
• iss228 there was a login and reload bug that caused Kunagi to deadlock in a loading view
• iss227 the admin can now set a default password for newly created users
• iss226 mail servers without authentication data were unusable

This Sprint we want to address the issue that has been complained about the most, namely the complete lack of documentation. The reason for that is that we wanted to release the software early and not get caught up in perfectionism and release date creep. Now that so many users actually want to put Kunagi into use, we reprioritized our future plans to provide basic documentation as soon as we can.

Of course, complete user documentation is not written over night, especially since we really want to capture the agile spirit we intended. But for starters, the software will get in-program explanations of all views and fields.

Not as visible, but equally important, we want to set up a framework for automatic testing of code and GUI, so that we can avoid introducing new bugs when deploying new versions.

Last, but not least, we have received quite an amount of good and helpful feedback during the last month. Thank you for that. Not only does it encourage us to work on the project, it provides hands-on information on what to focus on. It also lets us know how the software is perceived by people who have not been working on it for a year. We cannot provide that valuable information ourselves, so please feel free to keep on submitting your thoughts and ideas to help improve the software where it's needed.

The new version contains Stories scheduled for our current Sprint.

• User registration that allows users to create their own more or less persistent projects in the demo application,
• a downloadable version of Kunagi with a simple installation documentation,
• a blog can now be managed from the Administration -> Blog view,
• content from Kunagi can be exported via Apache Velocity,
• smileys have been substituted by a smaller and clearer set.

Related to our own project it means that

• we now have this blog and
• our Issue List, Product Backlog and current Sprint Backlog can now be seen on this website.

Additionally, we have some bug fixes, namely

• iss190 after the installation of Kunagi a default password notice is now displayed,
• iss181 Tasks are now deleted when carrying Stories over to the next Sprint,
• iss204 Issues that have been accepted as Ideas can now directly be converted to a Bug,
• iss148 in some cases date calculations were wrong,
• iss196 the software now runs GWT 2.0.4,
• iss194 the Burndown Chart in example projects no longer breaks when the user edits the current Sprint,
• iss88 the Sprint Report now contains information on who was Team, Scrum Master and Product Owner,
• iss158 Sprints are can now be referenced correctly using sprN (where N is a number),
• iss157 non-existing Wiki pages can now directly be created after a failed attempt to open them.

Kunagi is aimed at, but not limited to, software projects. The light nature of agile project management allows for use by both professionals and non-professionals, causing minimal overhead to the project. Therefore, it is also suitable for small projects done by virtual teams, i. e. teams that are scattered across the world.

Using Kunagi's web interface, it is possible to access project related data from anywhere. Despite being an online application, the powerful interface is built to keep up with the flexibility of desktop software, as it makes use of asynchronous technology employing the Google Web Toolkit (GWT).

Last, but not least, it is important to us that the tool helps people get their work done. We understand that it is therefore important for the tool to be not only suitable for project management, but also be accessible, offer a coherent work flow and be fun to use. For this reason, we have been using Kunagi for it's own project management, once it was ready to provide sufficient functionality for our needs. Moreover, after the tool's release, we will provide additions, enhancements and updates on a regular basis.