This means:

• Removing the tire gem
• Picking an appropriate alternative
• Making it all work with the newer query dsl

This makes it less convenient for people doing planning poker via their mobiles.

There should at least be a link or a collapsible thing that displays the task description, or it's easy to miss them.

Firstly, thanks for making this great software!

Planning poker mode only really works when every estimator joins the planning poker at the same time. If anyone clicks the link after someone else has already estimated, they won't see the estimates that have already been made.

But as long as the scrum master joins at the start, they will see them all, so it doesn't matter too much.

I am able to setup agileista server on my Ubuntu Linux dev box.
But unable to login/signup. I have tried multiple mail ids but still not able to login.
I didnt received any confirmation mail so to unblock myself I manually updated people table to confirm my user.
But still cant get pass login page :(.

Can you please help.

I wonder if you have considered the ability to add custom columns/statuses to the sprint board. Or was it a deliberate decision to keep things simple by only having three columns?

A colleague edited the notes of a story. I had added a bunch of tasks at the same time, and when I tried to save my changes, a red error bar appeared saying that another person had edited the story, which is great (thanks for implementing that!) but it doesn't help me to fix it. It was unclear whether the changes had been merged (they hadn't) or whether it was just my changes being shown (it was).

One thing I really like about Wikipedia editing is that if there is an edit conflict, they show a diff so that you can see the difference between the other person's new version and your new version. Well, in practice I find it a bit confusing, but in principle it seems like a good idea to show both versions.

It should either not scroll the page at all, or scroll to the new task.

i.e. the month is used instead of the day name. The other days are fine.

Our sprint runs from Monday for 2 weeks, by the way.

Investigate how bad performance would be without it.
Consider removing use of Redis to prevent complexity in code base.

Our sprints run from the end of the sprint planning meeting until the start of the review meeting, which is at 10:30am on alternate Mondays - so there is a little bit of time on the Monday morning at the end of a sprint to do some final work and update the board. However, by default, when a sprint is created, the last Monday isn't included in the sprint, so the board can't be updated if the sprint was created in the default way (without moving the end date forward by one day).

It would be useful to have a way to easily copy an incomplete story back into the backlog, because if the story is almost complete it might make sense to keep it the same (apart from the estimate, if the team is following the "re-estimate incomplete stories" approach).

I assume this is happening because the code that receives the form submission isn't checking if the story data has changed since the form was loaded, but I haven't checked if that is indeed the reason.

It would be really useful to be able to attach files to stories.