| 2006-01-13 16:41:58 |
Brad Bollenbach |
bug |
|
|
added bug |
| 2006-02-21 19:19:11 |
Dafydd Harries |
malone: severity |
Normal |
Wishlist |
|
| 2006-02-21 19:19:11 |
Dafydd Harries |
malone: statusexplanation |
|
|
|
| 2006-05-20 13:51:51 |
Diogo Matsubara |
malone: status |
Unconfirmed |
Confirmed |
|
| 2006-12-05 23:17:11 |
Matthew Paul Thomas |
description |
Malone should handle scenarios where two people edit the same page at the same time. For example (sorry, I'm too underslept for creativity):
1. User A visits +edit.
2. Shortly after, user B loads +edit.
3. User A changes the field "foo" to value "bar".
4. User B changes the field "baz" to value "spam".
5. User A clicks "Save" and saves the changes.
6. User B clicks "Save" and saves the changes.
User B should see a conflict message, and be given a chance to resolve any conflicts in the form submission. |
Launchpad should handle scenarios where two people edit the same page at the same time. For example:
1. User A visits +edit.
2. Shortly after, user B loads +edit.
3. User A changes the field "foo" to value "bar".
4. User B changes the field "baz" to value "spam".
5. User A clicks "Save" and saves the changes.
6. User B clicks "Save" and saves the changes.
User B should see a conflict message, and be given a chance to resolve any conflicts in the form submission.
Real-world examples include OOPS-137A366 and bug 74081. |
|
| 2006-12-05 23:17:11 |
Matthew Paul Thomas |
title |
Malone should handle mid-air-collision |
Handle mid-air collisions in bug reports |
|
| 2006-12-05 23:18:25 |
Matthew Paul Thomas |
malone: importance |
Wishlist |
Low |
|
| 2009-04-07 11:33:56 |
Matthew Paul Thomas |
description |
Launchpad should handle scenarios where two people edit the same page at the same time. For example:
1. User A visits +edit.
2. Shortly after, user B loads +edit.
3. User A changes the field "foo" to value "bar".
4. User B changes the field "baz" to value "spam".
5. User A clicks "Save" and saves the changes.
6. User B clicks "Save" and saves the changes.
User B should see a conflict message, and be given a chance to resolve any conflicts in the form submission.
Real-world examples include OOPS-137A366 and bug 74081. |
Launchpad should handle scenarios where two people edit the same page at the same time. For example:
1. User A visits +edit.
2. Shortly after, user B loads +edit.
3. User A changes the field "foo" to value "bar".
4. User B changes the field "baz" to value "spam".
5. User A clicks "Save" and saves the changes.
6. User B clicks "Save" and saves the changes.
User B should see a conflict message, and be given a chance to resolve any conflicts in the form submission.
Real-world examples include OOPS-137A366 and bug 74081.
See also bug 45304, about the Not Found error from submitting a change to a bug report that was retargeted in the meantime. |
|
| 2009-06-18 09:36:10 |
Graham Binns |
malone: importance |
Low |
Medium |
|
| 2010-08-22 10:32:53 |
Vish |
bug |
|
|
added subscriber Vish |
| 2010-10-22 20:30:33 |
Emmet Hikory |
bug |
|
|
added subscriber Emmet Hikory |
| 2011-05-30 08:08:17 |
William Grant |
removed subscriber Canonical Launchpad Engineering |
|
|
|
| 2011-09-20 20:38:52 |
Robert Collins |
launchpad: importance |
Medium |
Low |
|
| 2011-09-20 20:39:11 |
Robert Collins |
summary |
Handle mid-air collisions in bug reports |
Multiple people editing (any) object in Launchpad may overwrite the other persons changes |
|
| 2011-09-20 20:39:21 |
Robert Collins |
summary |
Multiple people editing (any) object in Launchpad may overwrite the other persons changes |
Multiple people editing any object in Launchpad may overwrite the other persons changes |
|
| 2012-01-05 04:47:54 |
Robert Collins |
summary |
Multiple people editing any object in Launchpad may overwrite the other persons changes |
Multiple people editing any object in Launchpad may overwrite the other persons changes (via mid-air collisions) |
|
