Hi Nathan,

> I suspect this has been discussed before, but I couldn't find it. I have
> had for a few months now an issue when I do my sprint planning in the
> "Team members' capacity planning" frame of the team's sprint page I see
> a number of Trac users listed who are not members of the team. None of
> the stories attached to the sprint are assigned to any of these other
> Trac users (I suppose it's possible that some of the requirements or
> tasks associated with those stories might be, but I don't think that is
> the case either).

This is strange - could you please double-check that only the team
members that are supposed to be in a team are actually in them?

One way to check would be to log in as admin and go to
Admin>Agilo>Teams>$TEAMNAME.

> This would all be fine except that I am also not allowed to set the
> capacity for these Trac users to 0 - I get a Trac error when I attempt
> to do that that states "AttributeError: 'NoneType' object has no
> attribute 'calendar'" mt assumption has been that this error is because
> some of those users are not actually team members for the team assigned
> to the sprint.

> Has anyone seen this and does anyone know what I can do to resolve it
> other than adding those Trac users to the team and never giving them any
> capacity?

Not sure whats happening there, but could you please report the version
of trac and agilo that you use?

One way to do this is to log in to agilo as an admin and visit "About
Trac" in the upper right corner. Then copy the system information table.

Regards,
Martin
-- 
Follow Agilo on Twitter: http://twitter.com/agiloforscrum
-----
You received this message because you are subscribed to the Google
Groups "Agilo for Scrum" group. This group is moderated by agile42 GmbH 
http://www.agile42.com and is focused in supporting Agilo for Scrum users.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/agilo?hl=en

Reply via email to