General
171 results found
-
Saving 'Export to CSV' settings
I would LOVE the ability to save my Export settings (the columns I choose). Either a global save (last used) or a save to a named export settings.
2 votes -
Allow users to change an Issue to a User Story
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.
6 votes -
Improved developer usage metrics
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.
1 vote -
Color user stories by epics
Enable to set the color of User Stories by their Epics, so that you can see clearly what this US relates to.
3 votes -
More granularity to Slack integrations
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.
32 votes -
Provide Integration with Glip
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
10 votes -
remove special character limit from passwords
Please add more special characters to the password whitelist.
The whitelist is pretty restrictive with only "@#$&%^!(){}_+|~-"
Why is there even a limit?1 vote -
Add project name to PDF export of Issue Statistics Widget
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.
1 voteHi,
It is already known and planned, hopefully with our next release update in September 2015, PDF will have all the needed data.
Best Regards,
Yodiz Support Team -
Change owner when task/issue moved
When I move a task created/assigned by someone else into progress or done, I want Yodiz to automatically change the owner to my user.
3 votes -
Keep up the good work!
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.
4 votes -
More Accurate Burn Down Chart
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.
5 votesHi,
Thanks for the feedback.
Currently we have 2 options at Burndown chart, “Story Points”, which as you mentioned only moves when story moves to Done or accepted state.
Second Burndown is for Tasks (based on hours estimates).it is interesting option to have a graph, like you have explained that shows incremental progress based on number of tasks.
We will discuss with our team and hopefully will implement this soon.
Best Regards,
Yodiz Support Team -
Add numerical priorities, and allow sorting.
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!
20 votes -
should have a plain text editor
The bug/issue tracking feature of Yodiz is quite important for me. As an IT company our bug descriptions may contain some code snippet, html source snippet, special characters, etc. However many of these special code parts are transformed - html tags are removed after saving, special characters are changed, sometimes removed by the editor. Very often it would be simply easier to attach a line of code to the description instead of attaching it as a text file.
1 vote -
Dependencies
Current dependencies feature is OK, but the real use case for us is for people to look at the sprint and need to know what to do first or what to watch to know when their task is ready to start.
Our suggestion would be to put a blocked indicator on the card (possibly red color) that has a mouseover to tell you what task is blocking it. The top blocker should have a different indicator (maybe same icon in same place, but green instead of red?) so that it is obvious what needs to be done first when you…
6 votesHi,
We are going to link the “Block” status with “Dependency is Block by” features and also will add the different color code for blocked items.
So in a way most of your suggestions are in pipeline and we will make them public once they are ready in our upcoming releases.
Best Regards,
Yodiz Support Team -
Tighter integration with SVN/Git
It would be great if your tool could integrate even tighter with tools such as SVN and Git. For example so that one could look at changesets or view file source directly from within your app.
14 votesThanks for the feedback, we have added this to our Backlog and will analyze it further.
Best Regards,
Yodiz Support Team -
Allow users stories to span more than one sprint
Users stories can be assigned to a sprint, but not tasks. Sometimes one user story has 2 tasks, but only one gets done in the sprint. My only option is to move the entire user story to the next sprint (including the completed task), so I lose my statistics on velocity for work accomplished and velocity for the previous sprint.
The only good workaround is to build a user story for every single task and actually use Epics to group them together. But that just makes a task a pointless extra step.
35 votes -
Wiki page
Projects could have a wiki page with relevant infos about the projects.
14 votes -
Integrate to Harvest
We are using Harvest (http://www.getharvest.com/) for tracking working hours. Since the working hours are the basis of our billing (as for most of project companies), they need to be up-to-date.
As a result, the sprint task hours are not that well up-to-date. Syncing between the two systems might help - reporting the hours spent to Yodiz and auto-exporting them into Harvest would remove the need for double-bookkeeping.
Or alternatively, if one could easily see that there are some 15 hours in Harvest that have no explanation in Yodiz would raise some very valid questions that we might need…
8 votesHi,
Thanks for the feedback.
Along with other improvements we are working on releasing ZenDesk integration and after that we will definitely priortize integration with Harvet/tracking hours service.Will update status once we have planned the implementation.
Best Regards,
Yodiz Support Team -
US belongs to more Epics
Let User Stories to belong to more Epics
1 vote -
Use estimated hours of user stories in sprint resource manager
Use estimated hours of user stories (plan estimate field) in sprint resource manager (add option to use hours estimated on tasks or on user stories).
1 vote
- Don't see your idea?