This is very important especially for teams that are newly adopting Scrum. Reviewing prior story points and tasks would help a lot in estimation and newly joined developers.

Thanks for this great tool and such a transparent collaboration with your users.

There was a bug that prevented completed Stories from appearing in the Sprint History view (iss506). You can see only the text representations there, however. This Story is about displaying the Stories like in the Product or Sprint Backlog, after they are completed.

In the upcoming Release (0.20) iss506 is fixed.

I agree this is a key feature. Having access to completed stories/tasks not only makes estimation a lot easier (in the current version you cannot access task comments e.g. to see why a task took so long) but also helps to communicate the scope of completed work to the client.

We can see the completed stories and tasks under those in the sprint history. But we can not see any details like comments for the stories and task detailed descriptions.

As mentioned above by other users, it helps a lot to know the detailed history.

Hi,

Is there any update to the above comment from me. I installed latest version of Kunagi, I can see the story title and tasks title (with a link on task name) in the sprint history. But after I click on the task link, no details of the task are shown. When we refer back to the previous sprint tasks for any details, it will be helpful to see detail description of the task.

Thanks,
Aruna Gutta.

This is due to a lack of a "cemetary view". Kunagi cannot display any entities from past Sprints (i. e. Stories or Tasks, with all their appending entities like Comments), because it does not know in what view to open them. We will discuss this and possibly reprioritize this Story to be done sonner.

For what it's worth, we feel that this is a key feature that is missing from Kunagi -- and is driving our search for a replacement. We need to have access to previous User Stories so that we can accurately determine what to look for during smoke testing (which often takes place many weeks after the end of the Sprint).

++ for reprioritization.

We would also like to see this given high priority. It is the most consistently noticed lack by all new users in our organization.

Thanks for incorporating this feature with 0.23.
Although its a bit buggy, the data is very useful.

Yes, it is slow and buggy. We will try to make it more usable during next releases.