Summit

Fetch all subscribes from Blueprints when cross-checking

Bug #884610 reported by Nigel Babu on 2011-11-01

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Summit	Triaged	High	Unassigned

Bug Description

The XML generated in +temp-meeting-export does a check to see if the subscriber to a blueprint is a participant in the sprint. This is now creating problems since we now use two sprints, one for LDS and one for UDS.

Part of the solution is already in summit - we import blueprints from both UDS and LDS. The second part would be to cross-check subscribers in another cron. This bug is to track that feature.

See original description

Nigel Babu (nigelbabu) on 2011-11-01

Changed in launchpad:
assignee:	nobody → Nigel Babu (nigelbabu)

Brad Crittenden (bac) on 2011-11-01

Changed in launchpad:
status:	New → Triaged
importance:	Undecided → High

Julian Edwards (julian-edwards) on 2011-12-01

no longer affects:

launchpad

Revision history for this message

Nigel Babu (nigelbabu) wrote on 2011-12-01:

If anyone wants more details to help implement this, feel free to get in touch, otherwise, I will deal with this myself.

summary:	- Change the attendee in +temp-meeting-export + Fetch all subscribes from Blueprints when cross-checking
description:	updated
Changed in summit:
importance:	Undecided → High
status:	New → Triaged

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.