When you have 50+ stories on the backlog and you go to the 2nd page of, the button for the 2nd page disapears
Even when you go back to the first page it stays hidden, and the amount of stories found is also limited to only the first page.

This if fixable to change the amount of stories shown

visuals:
[prev][1][2][next] Displaying 1 - 50 of 53

on clicking next/2 it becomes:
[prev][1][next] Displaying 51 - 53 of 3

finaly when clicking prev/1:
[prev][1][next] Displaying 1 - 50 of 50

I have hundreds of issues in my issue tracker - currently I can find no way to apply a tag to a small number of items and then remove these from view using a tag filter.

Something like "NOT #example" or similar would be good, as it then follows conventions in SQL Server

Add an option in the profile to allow for a daily summary update email instead of being emailed every time something changes.

At the moment when you start a project or are setting up Yodiz you get lots of emails as Epics, Stories and Tasks are created and updated. It would be good to have a "Setup Mode" where you can select to get a summary email daily instead of all of the individual emails.

Once the project is underway and the right people are assigned to the right pieces you can turn individual notifications back on again.

Please allow us to toggle 'select all' projects in the Project dropdown. I have days wherein i want to see where all of my projects are and clicking them one by one is a pain.

i.e.

If I search for "sampleText" it returns 1000 results. But these results are too big to browse to.

As a user, I would like to search for this value "sampleText" and exclude this value "exclusionText" from the results/search.

It would be very helpful to add a Requirement Management feature to the site. Before dealing with Epics, Stories and tasks we have to gather, organize and translate the requirements. It would be great to have a feature that offer methods of keeping track of requirements, creating a work breakdown structure integrate it with the Gantt chart feature.

Estimated effort + logging effort diretcly in User Stories without the need of Tasks.

Allow global epics to be picked in dashboard plugins and/or allow epics to span multiple projects.

Right now you can have a project specific epic and track it, but only add stories from that project. Or you can have a global epic and assign stories from multiple projects but not track it in the dashboard. None of which is sufficient.

Issues sometimes get added when they should be User Stories and it would be useful to be able to convert from Issue to User Story as well as User Story to Issue as well.

Provide better developer metrics and reporting. I would like to know what developers are doing each day in Yodiz - how many bugs the close, which bugs, etc.

Enable to set the color of User Stories by their Epics, so that you can see clearly what this US relates to.

Thanks for the slack integration. We'd like greater control and granularity to what is pushed to slack. "Updates" is far too open. We'd like only updates in moving status. Or only comment updates. Or only re-assigns of issues, etc. This level of granularity would better allow us to control the amount of chatter in channels from Yodiz. Today, these are far too chatty in Slack with just something as simple as "Updates" enabled.

We use Glip at our organization as a team collaboration tool. Would be great if Yodiz has integration with Glip similar to how integration for Slack exists right now

Please add more special characters to the password whitelist.
The whitelist is pretty restrictive with only "@#$&%^!(){}_+|~-"
Why is there even a limit?

In the User Dashboad area, you can select widgets and then export the result to a PDF. When I do this for Issue Statistics, the pdf comes out just fine, but it lacks the project name. This way, I have to export a widget, change the name of the pdf and only then can continue to the next one.

Just saw the beta UI today and I really like it! Good work guys. I really like how I can see bugs and user stories on the same page now, and quickly enter tasks all in one spot.

Your burn down graph doesn't seem to be accurate. It only reflects "completed" stories, and does not account for completed tasks of a story.

All burn down charts I have worked with, they take the total points of a user story, and divides the number of tasks. This more accurate calculation reflects a burn down chart.

Otherwise you get what we have which is a very flat "stair case" burn down chart, where progress is only reflected when stories are completed.

Tasks should be rewarded on a burn down chart for completed.

Allow numerical priorities, say 0-100, and allow sorting on the sprint board by priority.

This will allow the developers to manage their tasks better, and focus on those with highest priorities, which would be especially useful if a sprint is running behind!