| 2010-07-08 11:23:37 |
John Lea |
bug |
|
|
added bug |
| 2010-07-08 11:23:57 |
John Lea |
tags |
|
acceptance-test |
|
| 2010-07-08 11:27:04 |
John Lea |
ubuntuone-client: assignee |
|
Ubuntu One Desktop+ team (ubuntuone-desktop+) |
|
| 2010-07-08 13:03:04 |
John Lea |
description |
After enabling Ubuntu One for a folder, the parent folder should no longer display the 'Enable' button. A message should be displayed informing the User that the they cannot Ubuntu One enable the folder because it contains a child folder that is already Ubuntu One enabled.
To reproduce:
1. Enable Ubuntu One for a folder.
2. Immediately browse to the parent folder.
Current outcome: the 'Enable' button is still displayed in the parent folder
Desired outcome: The 'Enable' button should no longer be displayed. A message should inform the user that they cannot Ubuntu One enable the folder because it contains a child folder that is already Ubuntu One enabled should be displayed.
See variation 5.b of use case 2.1.A in the File Sync spec
(I just added this variation to make sure this scenairo is captured, it wasn't part of the original spec ;-) |
After enabling Ubuntu One for a folder, the parent folder should no longer display the 'Enable' button. A message should be displayed informing the User that the they cannot Ubuntu One enable the folder because it contains a child folder that is already Ubuntu One enabled.
To reproduce:
1. Enable Ubuntu One for a folder.
2. Immediately browse to the parent folder.
Current outcome: the 'Enable' button is still displayed in the parent folder
Desired outcome: The 'Enable' button should no longer be displayed. A message should inform the user that they cannot Ubuntu One enable the folder because it contains a child folder that is already Ubuntu One enabled should be displayed.
This is applicable to variation 1.c of use case 2.1.A in the File Sync spec.
|
|
| 2010-07-08 13:57:06 |
John Lea |
tags |
acceptance-test |
acceptance-test rhubarb |
|
| 2010-07-08 14:31:04 |
John Lea |
description |
After enabling Ubuntu One for a folder, the parent folder should no longer display the 'Enable' button. A message should be displayed informing the User that the they cannot Ubuntu One enable the folder because it contains a child folder that is already Ubuntu One enabled.
To reproduce:
1. Enable Ubuntu One for a folder.
2. Immediately browse to the parent folder.
Current outcome: the 'Enable' button is still displayed in the parent folder
Desired outcome: The 'Enable' button should no longer be displayed. A message should inform the user that they cannot Ubuntu One enable the folder because it contains a child folder that is already Ubuntu One enabled should be displayed.
This is applicable to variation 1.c of use case 2.1.A in the File Sync spec.
|
.
|
|
| 2010-07-08 14:31:59 |
John Lea |
summary |
Sync Polish - 2.1.A - After enabling Ubuntu One for a folder, the parent folder should no longer display the 'Enable' button |
Sync Polish - 2.1.A - After enabling Ubuntu One for a folder, the parent folder should display the 'partially enabled' state |
|
| 2010-07-08 15:10:06 |
John Lea |
description |
.
|
After enabling Ubuntu One for a folder, the parent folder should no longer display the 'Enable' button. A message should be displayed informing the User that the they cannot Ubuntu One enable the folder because it contains a child folder that is already Ubuntu One enabled.
To reproduce:
1. Enable Ubuntu One for a folder.
2. Immediately browse to the parent folder.
Current outcome: the 'Enable' button is still displayed in the parent folder
Desired outcome: The 'Enable' button should no longer be displayed. A message should inform the user that they cannot Ubuntu One enable the folder because it contains a child folder that is already Ubuntu One enabled should be displayed.
See variation 1.c of use case 2.1.A in the File Sync spec
Also see variation 5.b (I just added this variation to make sure the scenario of quickly returning to the original folder is captured as well, it wasn't part of the original spec ;-)
|
|
| 2010-07-12 11:45:13 |
Rodrigo Moya |
ubuntuone-client: status |
New |
In Progress |
|
| 2010-07-12 11:45:13 |
Rodrigo Moya |
ubuntuone-client: assignee |
Ubuntu One Desktop+ team (ubuntuone-desktop+) |
Rodrigo Moya (rodrigo-moya) |
|
| 2010-07-14 16:47:23 |
Launchpad Janitor |
branch linked |
|
lp:~rodrigo-moya/ubuntuone-client/no-enabling-on-udfs-parents |
|
| 2010-07-16 10:35:51 |
Rodrigo Moya |
ubuntuone-client: status |
In Progress |
Fix Committed |
|
| 2010-07-22 19:06:53 |
Joshua Hoover |
ubuntuone-client: status |
Fix Committed |
Fix Released |
|
| 2010-07-23 13:59:42 |
Rodrigo Moya |
ubuntuone-client: status |
Fix Released |
In Progress |
|
| 2010-08-19 10:48:24 |
Rodrigo Moya |
bug task added |
|
ubuntuone-client (Ubuntu) |
|
| 2010-08-19 10:48:37 |
Rodrigo Moya |
nominated for series |
|
Ubuntu Maverick |
|
| 2010-08-19 10:48:37 |
Rodrigo Moya |
bug task added |
|
ubuntuone-client (Ubuntu Maverick) |
|
| 2010-11-04 15:29:36 |
Rodrigo Moya |
ubuntuone-client: assignee |
Rodrigo Moya (rodrigo-moya) |
Ubuntu One Desktop+ team (ubuntuone-desktop+) |
|
| 2011-02-11 20:41:05 |
Joshua Hoover |
ubuntuone-client (Ubuntu Maverick): status |
New |
Won't Fix |
|
| 2011-02-11 20:45:27 |
Joshua Hoover |
ubuntuone-client: status |
In Progress |
Triaged |
|
| 2011-02-11 20:45:37 |
Joshua Hoover |
ubuntuone-client: importance |
Undecided |
Medium |
|
| 2011-02-11 20:45:41 |
Joshua Hoover |
ubuntuone-client (Ubuntu): status |
New |
Confirmed |
|
| 2011-02-11 20:45:47 |
Joshua Hoover |
ubuntuone-client: status |
Triaged |
Confirmed |
|
| 2011-02-11 20:45:53 |
Joshua Hoover |
ubuntuone-client (Ubuntu): assignee |
|
Ubuntu One Desktop+ team (ubuntuone-desktop+) |
|
| 2011-02-11 20:45:58 |
Joshua Hoover |
ubuntuone-client: importance |
Medium |
Low |
|
| 2011-02-11 20:46:03 |
Joshua Hoover |
ubuntuone-client (Ubuntu): importance |
Undecided |
Medium |
|
| 2011-02-11 20:46:19 |
Joshua Hoover |
tags |
acceptance-test rhubarb |
acceptance-test desktop+ nautilus rhubarb |
|
| 2011-02-11 20:46:31 |
Joshua Hoover |
ubuntuone-client (Ubuntu): importance |
Medium |
Low |
|
