0
W trakcie analizy

Activities tab that shows last updates on project

Mário Melo 12 lat temu Ostatnio zmodyfikowane przez Matthew O'Riordan (Founder) 12 lat temu 4
It would be nice to have an "Activities" tab, such as we have in Basecamp or Manymoon. It would be also nice if this tab had an RSS feed, like PlanBox does. It helps teams that work at distance to see what happened/is happening in the project.

Odpowiedź

Odpowiedź
W trakcie analizy
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?
Odpowiedź
W trakcie analizy
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?
Yes, kinda like that. In fact, that would be more useful if the other idea about Comment threads on User Stories were also implemented. The "Activities" could also have a RSS feed (here, at the top right corner, UserEcho does this), so people on project could follow the project from google reader, other RSS readers, and mainly mobile devices (that would be a huge benefit providing that every mobile OS has a RSS reader and you wouldn't need to develop easyBackLog for Android, iOS, BlackBerry, Symbian, etc).

I know exactly why you won't implement the "comment threads" for now and I agree: you must focus on the core business of your product. And I agree. Perhaps this idea should also be "freezed" for now, but keep that in mind for future releases.
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.

Matt
I think single updates would be better. Although it might generate some overflow, it is important to know what is happening. Also, if you detect a new kind of activity that should also appear in the feed (comments, sprint review, sprint results, etc) it would be easier to implement that.

The feeds should be unique per backlog, so people can follow only the feeds they're currently working.
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