email alert settings have all been reverted to immediately

Bug #382860 reported by Nat Katin-Borland
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KARL3
Won't Fix
Medium
Chris Rossi

Bug Description

I'm not sure if there's anything we can do about this, but after to migration to KARL 3, all users had their email alert settings for each community defaulted to "immediately," regardless of their preferences in KARL 2. This means that users will have to re-do all their email alert preferences. Obviously this isn't a huge deal, but we've had a few complaints.

Changed in karl3:
assignee: nobody → Paul Everitt (paul-agendaless)
importance: Undecided → Low
Revision history for this message
Paul Everitt (paul-agendaless) wrote : Re: [Bug 382860] [NEW] email alert settings have all been reverted to immediately

Nat, is this something you'd like scheduled and budgeted?

--Paul

On Jun 2, 2009, at 2:25 PM, Nat Katin-Borland wrote:

> Public bug reported:
>
> I'm not sure if there's anything we can do about this, but after to
> migration to KARL 3, all users had their email alert settings for each
> community defaulted to "immediately," regardless of their
> preferences in
> KARL 2. This means that users will have to re-do all their email
> alert
> preferences. Obviously this isn't a huge deal, but we've had a few
> complaints.
>
> ** Affects: karl3
> Importance: Low
> Assignee: Paul Everitt (paul-agendaless)
> Status: New
>
> ** Changed in: karl3
> Importance: Undecided => Low
>
> ** Changed in: karl3
> Assignee: (unassigned) => Paul Everitt (paul-agendaless)
>
> --
> email alert settings have all been reverted to immediately
> https://bugs.launchpad.net/bugs/382860
> You received this bug notification because you are a bug assignee.
>
> Status in Porting KARL to a new architecture: New
>
> Bug description:
> I'm not sure if there's anything we can do about this, but after to
> migration to KARL 3, all users had their email alert settings for
> each community defaulted to "immediately," regardless of their
> preferences in KARL 2. This means that users will have to re-do all
> their email alert preferences. Obviously this isn't a huge deal,
> but we've had a few complaints.

Revision history for this message
Anthony (agalietti) wrote :

Paul,

I spoke with Yalan and we feel this is very important. Does this bug apply to the entire user population or only some users?

Thanks.

Anthony

Revision history for this message
Paul Everitt (paul-agendaless) wrote : Re: [Bug 382860] Re: email alert settings have all been reverted to immediately

Not sure who it applies to, as we haven't picked the ticket up yet.

We're currently working on what we were told was the first priority,
and rolling out fixes from yesterday. Should we re-arrange what we
are working on?

--Paul

On Jun 2, 2009, at 4:53 PM, Anthony wrote:

> Paul,
>
> I spoke with Yalan and we feel this is very important. Does this bug
> apply to the entire user population or only some users?
>
> Thanks.
>
> Anthony
>
> --
> email alert settings have all been reverted to immediately
> https://bugs.launchpad.net/bugs/382860
> You received this bug notification because you are a bug assignee.
>
> Status in Porting KARL to a new architecture: New
>
> Bug description:
> I'm not sure if there's anything we can do about this, but after to
> migration to KARL 3, all users had their email alert settings for
> each community defaulted to "immediately," regardless of their
> preferences in KARL 2. This means that users will have to re-do all
> their email alert preferences. Obviously this isn't a huge deal,
> but we've had a few complaints.

Revision history for this message
Paul Everitt (paul-agendaless) wrote :

Increasing priority from Low ("this isn't a huge deal") to Medium ("we feel this is very important")

Changed in karl3:
importance: Low → Medium
Revision history for this message
Paul Everitt (paul-agendaless) wrote :

Migration bugs go to Chris.

Changed in karl3:
assignee: Paul Everitt (paul-agendaless) → Chris Rossi (chris-archimedeanco)
milestone: none → m17
Revision history for this message
Paul Everitt (paul-agendaless) wrote :

Per Nat/Anthony, we decided not to address this.

Changed in karl3:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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