Support forum for your suggestions, questions and to notify us of any issues you may encounter.
Geen vergelijkbare onderwerpen gevonden.
-1
Under review
Different resource rates in same backlog
A possible requirement might be to allow for different cost brackets on the same backlog (e.g. back & front end devs, maybe even designers). To maintain some simplicity we could still separate out by theme, so each theme has a fixed cost associated to it.
Antwoord
Matthew O'Riordan (Founder)
13 jaar geleden
I don't think we'll add this at this stage. I understand the need for this, but it will certainly add a lot of complexity when we're actually trying to simplify things. I'll keep this under review though and if other people feel this is needed, then we may well add this feature in future updates.
-1
Under review
Being expected to create themes before user stories seems counter-intuitive. I don't know what themes I want when I have just started, I just want to add user stories that I know about already.
Allow me to add stories first and then associate themes with them, not themes first.
Antwoord
Matthew O'Riordan (Founder)
13 jaar geleden
Hi Gary
Whilst I can appreciate that you don't necessarily think in themes at first, the entire interface revolves around the fact that you associate stories with themes at the outset.
Could you not just add a theme called General and file all stories under that, and later on move them into the themes you set up?
Also, as a work around solution on our side, if we added an Add story button that is visible when you first set up a backlog (right now that does not appear until a theme is created), would you be happy for that Add story button to simply set up a generic theme and add the first story into that? Would that suffice?
Matt
-1
Add key event comments, that show in the stats when you hover on the graph
What?
Simple piece of data just
Where?
To be shown as a milestone indicator on the burn up graph, so you can see the comment when you hover over it.
Why?
Basically the events that caused another batch of stories to be added to the backlog.
This would add a commentary to the burn up chart to answer the question "why is this chart going up?"
Who?
Anyone who cad add stories to the backlog.
Simple piece of data just
- Date
- Comment - free text
Where?
To be shown as a milestone indicator on the burn up graph, so you can see the comment when you hover over it.
Why?
Basically the events that caused another batch of stories to be added to the backlog.
This would add a commentary to the burn up chart to answer the question "why is this chart going up?"
Who?
Anyone who cad add stories to the backlog.
-2
Under review
Allow comments/replies on user stories
It would be nice if the comments on user stories were threads of discussion. This would allow teams that work at distance to improve collaboration over sprint itens, specially those where someone is stuck. It also would help to keep a history of the decisions made to solve the problems encountered.
Antwoord
Matthew O'Riordan (Founder)
13 jaar geleden
Thanks for the suggestion.
To be honest, when we designed the product we intentionally did not intend for the product to be a collaboration tool. We felt that when implementing agile, one to one communications and people over systems is where the focus should lie. easyBacklog is meant for scrum masters and product owners, not for the agile team themselves. Thus we provide all the tools a scrum master / product owner would need, setting up backlogs, assign stories to sprints (after or during the planning meeting), reporting on project progress as opposed to sprint progress which should really be done on a board shared with the team.
We'll certainly consider this for future versions should it become apparent that lots of people need this functionality, but for now unfortunately, we are going to have to leave this request under review.
Thanks again for the feedback.
Customer support service by UserEcho
