General
171 results found
-
Can I sort the tasks within one User Stories?
I want to put important tasks to top of each User Stories so that my teammates could know which task is urgent and should be done first.
also, each task may have dependencies, Task A should be done first before start task B, so the order of tasks is also important. But now the task can be sorted only according to the task ID, therefore, if I insert a task later, it always appear at the bottom of a User Story.3 votesThanks for the feedback, we have added this to our backlog and will get back to you with more details about implementation plan.
Best Regards,
Yodiz Support Team -
Epics, US, TK.
There could be an intermediate status for disaggregated epics (before it becoming a User Story)
3 votes -
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 test3 votes -
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 -
3 votes
-
slack integration - allow creating tasks from within slack
The current slack integration assumes we want changes made in yodiz pushed to slack.
We'd prefer the opposite; the ability to have tasks created within the slack channel and pushed to yodiz. Is this available?
3 votes -
Allow us to add in non-working days
I have seen that you have implemented an idea to not count weekends, but there is not a feature to say a specific one off day is not a working day. e.g. bank holidays in the UK, or even days that everybody is at a company day out.
3 votes -
create a pre-backlog-log
New userstories that appear in the backlog mess up the backlog organization. If they would appear rather in an unorganized pre-backlog (or whatever) then it would be easy to see which items have not yet been assigned a priority. Also the PO could move items that are in wrong spots in the backlog to the pre-backlog as she is prioritizing it and then re-prioritize the wrong ones.
Hard things like backlog prioritizing are done by "Divide and conquer". Please let me divide by implementing a pre-backlog.
2 votes -
Changes during sprint
We planned 2-week sprint. But after some time situation changed and we have to change to 3-week sprint and we added some US. The problem is with burndown chart. The "points done" line shows the actual stat day by day but "points estimate" line is show for actual size of sprint. It should have same approach - either day by day or based on current state...
I personaly favour the day by day aproach.
2 votes -
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 -
Add a "select all" toggle to the project dropdown
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.
2 votes -
Easier way to report your spent hours for multiple tasks
I keep on hearing from our UX developers (this is the second organization already) that they feel reporting hours to Yodiz tasks is too tedious. They keep on using Wunderlist and Harvester as an example.
What they want is a single tabular view of their task, and a possibility to distribute the hours of their working day between the tasks in one operation, and marking some of them complete. Even if it might be somewhat opposing the idea of task/scrum board itself (which I personally think is great!), it should be technically possible to show things their way, too.
2 votes -
Text search within "add related bug" function
When searching for related bugs one cannot even search into the titles of bugs. This then requires a two step process to search for the right bug and then remember the number of the other bug in order to link it.
2 votes -
Allow stories and issues to be associated with multiple projects
I'm a web developer. I have a few cases where one company has 3 sites that are almost the same, such that i find myself fixing the same bugs on all 3 sites, and making the same stories for all 3 sites.
We need to have a way to apply a story and issue to multiple projects.
For instance, if a manager tells me "I want to have you change the logo on all of our programs", with each program being a project i'd have to enter that story multiple times for each one.
Also, if a bug is found…
2 votes -
List all Dependencies in the Dashboard with option to filter
List all dependencies in the Dashboard with option to filter and/or sort rather than forcing user to view dependencies on only Tasks or User Stories at any point of time (as it exists now). It will be good to have the option to see all dependencies in a project.
2 votes -
2 votes
-
assign user-based colors on Kanban wall
Although users who own tasks are depicted on those tasks, the picture is quite small so it can be hard to distinguish one from the next. It would be nice if one could also set a color per user that shades the task box (or part of it) when a user owns it so you could tell them apart easily.
2 votes -
Global Epics in Dashboard
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.
2 votesWe will add support for Global Epics to be added to Dashboard
-
color issue
in edit , any user can changue the color of the div or the windowr for the reason is because a lot of programers can have a color assigned so when a programer ends a issue one tester can see if the issue is ready for test and when the tester ends, a tester can changue the color :
for example an issue is resolved changue to green(the programer ends the issue) when te tester ends him test he can changue the issue to blue (indicating the issue resolved ) and when the tester see if the issue its not…2 votes -
Improve Release management UI
A better UI to manage Releases instead of a pop-up.
2 votes
- Don't see your idea?