launchpad-users team mailing list archive
Mailing list archive
Re: Beta team: better bug subscriptions now enabled
On May 17, 2011, at 5:09 AM, Jonathan Lange wrote:
> On Mon, May 16, 2011 at 7:33 PM, Benji York <benji.york@xxxxxxxxxxxxx> wrote:
>> On Mon, May 16, 2011 at 12:48 AM, Brian Murray <brian@xxxxxxxxxx> wrote:
>>> On Fri, May 06, 2011 at 12:07:02PM -0400, Benji York wrote:
>>>> There's no single place that lists all your subscriptions, but you don't
>>>> have to find a bug to manage the notifications of a particular pillar.
>>> This certainly seems to be a list of my subscriptions for multiple
>> Unfortunately that page is deprecated. That's why there aren't any
>> inbound links to that page (or shouldn't be, let us know if you find
> Why is it deprecated?
Deprecated is perhaps the wrong word. I would describe it as "never released."
The page was done before yellow squad and without feature flags. The rest of LP had no link to it. AIUI, this obscurity was intended as a release mechanism, in lieu of feature flags.
The page was never deemed ready for release. It is not updated to the new terminology, and it does not follow the new JS-based UI patterns. Also, to my knowledge, the design was never user tested.
We could have removed the obscured page easily enough, but some power users who knew the secret still found it useful, and we have had plenty of other work to do, so I have never scheduled the task nor considered it to be of particular importance. However, since the page is now publicized here, perhaps we should remove it to prevent user confusion (for instance, none of the UI the yellow squad did describes subscriptions with multiple "filters"; we present it as multiple subscriptions).
As we've said in the past, we wanted to provide this see-all-your-subscriptions functionality, and it is described in the LEP ("nice-to-have") and in the user documentation draft that Benji wrote early on as a design artifact. However, this work should start with a user-tested design consistent with the rest of our related UI, and I continue to believe that such a design would result in a rewrite of the current page.