Skip to content

General

171 results found

  1. Traversing of bugs and tasks should be made easy

    I think we should have a link or button to see the next and previous bug just like we have buttons for viewing mails in gamil.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Poll specific branch in github

    Currently yodiz tracks all branches which adds to duplicate commit history when merging branches to master.

    For example:

    IF I commit "@T45:R Completed task number 45"

    to a branch - "branchAbc"

    It will show up in the history of Task 45...

    When I merge "branchAbc" to "master", it shows up again!!

    Yodiz should allow me to pick which branch I would like to poll, or poll master only by default.

    This can easily be done by parsing the webhook sent by github...

    The first line of the json request sent to yodiz contains the line:

    {
    "ref": "refs/heads/master"...

    Which gives…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Thanks for the feedback. Indeed it is a good idea. We have now added to our backlog and hopefully it will be implemented in our next release (March-April).
    Best Regards,
    Yodiz Support Team

  3. consider having a minimum offset to click buttons on the task

    I sometimes use a wacom instead of a mouse, and it is difficult to log time because most times when I click on the clock it thinks I drag instead of click

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. make it possible to flag tasks

    It would be really useful for the way that we use Yodiz if you could flag tasks up almost similarly to bugs, so crucial tasks etc.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Create a sprint for more than one project at a time.

    This is NOT about sharing one sprint across several projects. It's simply about a needed convenience.

    I have many projects. They all run on the same sprint schedule. As such, when it is time for me to create a sprint.... I must go through the steps to create a single sprint... a dozen times.

    This request is for you to allow a sprint to be created (It's Title, its start/end dates, show weekends option, and auto add all resources) and "applied" to all projects I select from my entire list of projects.

    This would allow me to go through…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Implement user stories mapping functionality to aid release planning

    A prioritized user story backlog helps to understand what to do next, but is a difficult tool for understanding what your whole system is intended to do. A user story map arranges user stories into a useful model to help understand the functionality of the system, identify holes and omissions in your backlog, and effectively plan holistic releases that delivery value to users and business with each release.

    Some reference material would be:
    http://www.agileproductdesign.com/blog/the_new_backlog.html
    http://agileproductdesign.com/writing/how_you_slice_it.pdf

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Have the duplicate and move/copy leave the duplicate in the OLD sprint...

    Hi,

    I've been using the 'duplicate and copy/move' feature. I think it's quite nice. One thing I have noticed is, when I duplicate something and copy/move it's tasks, the original stays in place and the new ones go to the destination sprint. This has the effect of causing my developers to now have to be made aware of the NEW USer stories and tasks.... when... in reality... they individually have not changed tasks.

    My suggestion is that you leave the NEW ones in the OLD sprint and move the original into the new sprint. This will provide some nice continuity…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Thanks for the feedback, we are analyzing this feedback regarding the adjustments to leave new user story in place and move the original one to next sprint.

    We will update more soon.

    Best Regards,
    Yodiz Support Team

  8. Story/Task Description Editor View

    As of now the application allows to enter HTML Description for Story/Task using WYSIWYG Editor.

    But when we actually add some TABLES HTML it does not show up in the actual view. When you click edit, it come up, but in VIEW mode, it does not visible as TABLE.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Make it possible for all users to access all projects

    I signed up "Professional" because your description says "unlimited projects."

    We're a start up. I have several projects and I would like to invite up to 5 people to these projects. It seems like I have to pay for access to each project. Based on your description of "professional user" for which I signed up with, I though I could have five users who would have access to any project.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. A TimeSheet that allows you to see "tasks" OR "user stories" would be great...

    We often have user stories that have several tasks, each of which may be completed by a different dev in parallel. Would be nice to see finer grained time sheet.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Different number of hours for team-members

    We have several team-members that are only available part-time. It is rather difficult to calculate how many off hours they have, so it would be easier to generally set how much a certain member is available any given day.
    This might be interesting both on the user and on the Sprint settings!

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Add password requirements on password reset menu

    There is no notification about bad password on password reset menu. So, password may contain invalid chars or may be too short after reset. However, you can't authorize using this password.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. estimate choosing dropdown

    The old estimate choosing dropdown menu on the scrum board was better and I could use it more quickly. With the new slider I can hardly make precise positions (and times) so I have to type in the hours.
    With the old one I could simply choose from the dropdown, it was way quicker.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Yodiz iPad app has incorrect demo suggestion

    It suggests using Demo/Demo while the correct sign in is demo/demo as I found out on your web site.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Disponibilizar versão em Português (Brasil)

    Prezados, a ferramenta é ótima!
    Entretanto, seria melhor ainda se diponibilizassem uma versão traduzida para Português (Brasil).
    Dessa forma, possibilitará ao usuários de idioma português uma melhor experiência com a aplicação.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Assign tasks to sprints

    Stories may be large items, with multiple tasks - with the story assigned to a release. A story may span multiple sprints, so it would be useful to be able to just assign a story to a release and the individual tasks to each sprint.

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. 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 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Provide customizable work flow for Kanban and Bug Tracking

    Flow dependent processes like Bug Tracking and Kanban should have customizable work flow mechanism to enforce their processes respectively. For example:

    a) when a bug is submitted, it should always go to QA for verification before sending to developer for bug fix,
    b) a QA rejected task/user story should always be returned to developer instead of sending for further system test

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. 2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

General

Categories

Feedback and Knowledge Base