[2.1, FUJ] Please update FUJ text to match latest copy doc chages

Bug #1628067 reported by Maria Vrachni on 2016-09-27
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Medium
Andres Rodriguez

Bug Description

MAAS bzr5400

The copy in the whole of user journey needs to be updated based on the copy doc found here:
https://docs.google.com/a/canonical.com/document/d/1hLt5F4FSMc2EdgTHeHH2V0pPwVo9tTscvWrie71Dfic/edit?usp=sharing

Bug description:

* Current result:

Given I am in the first use journey
When I am reading the description of sections/ fields etc
Then I see an old version of the copy

* Expected/ correct result:

Given I am in the first use journey
When I am reading the description of sections/ fields etc
Then I need to be able to see the latest copy edited on the 21st September

OS X Sierra

Chrome, 53.0.2785.116 (64-bit)

Related branches

Changed in maas:
importance: Undecided → Low
status: New → Triaged
milestone: none → 2.1.0
summary: - [FUJ] Copy is not consistent with the copy doc
+ [2.1, FUJ] Copy is not consistent with the copy doc

@Maria,

The copy was updated after the designs. We need to follow a workflow here. I think the designs should be udpated.

Changed in maas:
importance: Low → Wishlist
status: Triaged → Confirmed
status: Confirmed → Incomplete
importance: Wishlist → Medium
Blake Rouse (blake-rouse) wrote :

Yes, its sad to see the copy after I have already started the implementation. Actually in this case I think it was landed before the copy was even provided.

summary: - [2.1, FUJ] Copy is not consistent with the copy doc
+ [2.1, FUJ] Please update FUJ text to match latest copy doc chages
Changed in maas:
assignee: nobody → Andres Rodriguez (andreserl)
status: Incomplete → In Progress
Changed in maas:
milestone: 2.1.0 → 2.1.1
Changed in maas:
milestone: 2.1.1 → 2.1.2
Changed in maas:
milestone: 2.1.2 → 2.1.3
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers