+temp-meeting-export only shows subscribers that are attendees

Bug #1179736 reported by Ursula Junque on 2013-05-14
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself
High
Unassigned

Bug Description

This next vUDS isn't requiring people attend the sprint in Launchpad in order to participate of the discussions, but +temp-meeting-export used by Summit only shows blueprints' subscribers that are registered as attendees. According to cjohnston this will cause problems.

Ursula Junque (ursinha) on 2013-05-14
Changed in launchpad:
status: New → In Progress
Ursula Junque (ursinha) on 2013-05-14
Changed in launchpad:
importance: Undecided → High
Ursula Junque (ursinha) wrote :

Setting back to triaged as this requires further discussion. Simply enabling +temp-meeting-export to display all subscribers might cause timeouts, so we need to see if there are other alternatives or even measure this one better to avoid performance problems. Also StevenK and wgrant found it better not to make any changes on blueprints in the middle of a UDS.

Changed in launchpad:
assignee: Ursula Junque (ursinha) → nobody
status: In Progress → Triaged
Chris Johnston (cjohnston) wrote :

Doing this export for only future/current sprints would be fine, then disabling it after a sprint is complete.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers