Ваші коментарі
Ok, I'll give it some thought and see what's possible. I think single updates would be useful, but it will need some grouping i.e. if you edit a single story 5 times in the space of 5 minutes, then really it should only be considered one update.
Thanks for the suggestion
13 років тому
They all look fine, however the following ones are a bit long. Do you think there is any way to abbreviate (in English we use pts instead of points for example):
21.0 abgeschlossene Punkte
15.0 erwartete Punkte
21.0 zugewiesene Punkte
Thanks,
Matt
Matt
Hi Carola
Matt
That would be great, I will send you a link shortly to a Google Doc where I would need the translations. Thanks (in advance) for providing these.
Matt
Thanks so much, glad you like the tool. If you have any questions or suggestions, please do fire away.
Hi Mário
Just given some thought to this and I think it would be quite easy to add a simple RSS feed, however I am worried it would be drowned in activity. Do you envisage that every single edit would fall into the RSS feed, or do you think it would be better to batch up activity such as:
- Jim - 10h30 - Updated Backlog 'ABC', 24 changes
- Michael - 10h40 - Assigned a 3 stories to Sprint 1
- Jim - 11h00 - Changed status of 2 stories in Sprint 1
The alternative would be that each change would generate a single RSS item, but I am worried the flood of items would make the RSS feed unusable. What do you think?
BTW. The aggregated summary is a lot harder as we would need to keep track of all changes, and once it appears the user has stopped making changes, we'd log that group of changes as one item.
BTW. The aggregated summary is a lot harder as we would need to keep track of all changes, and once it appears the user has stopped making changes, we'd log that group of changes as one item.
Matt
Ah, that's quite a nice idea. I am a bit concerned however that there wouldn't be a huge amount to show though i.e. it would say something like 'John edited story X of backlog Y', and "Story Z was assigned to Sprint X". Is that what you were after, or were you imagining more information?
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.
This is also fixed now, apologies, a few bugs were introduced recently when adding support for auto-linking and concatenating URls
Good spot Martin, and apologies if this caused you to lose any data. I believe the problem is now fixed and was introduced a few days ago when we released automatic URL linking and concatenating for acceptance criteria and comments
Hi Mário
Thanks for the suggestion. Unfortunately I'm reluctant to add even more fields at this stage as a lot of the feedback we've had has been to reduce the number of fields if possible as it's already quite busy with information. Saying that, I'll keep a note of your request here, and if other start asking for something similar, I'll certainly consider a way to integrate this.
In terms of Theme importance, the idea is that you order the themes by importance, and you order your stories by importance. So whilst there isn't a nice formula to give you a relative importance vs points required, it is quite straightforward to deduce this by simply looking at the backlog.
Matt
Служба підтримки клієнтів працює на UserEcho
