harvest-dev team mailing list archive
-
harvest-dev team
-
Mailing list archive
-
Message #00406
[Bug 618799] Re: Adding a note to an opportunity is not obvious
Just edited this to be more generic :)
** Description changed:
- To add a note to an opportunity, a user currently needs to click the
- Edit button and use the new_note character input. This is not obvious
- and will probably result in the feature being missed.
+ Right now, adding a note to an opportunity, setting a difficulty level
+ or marking an opportunity Applied (see bug #581719) involves first
+ knowing that the options exist, then navigating to the unclearly
+ labelled “Edit” form.
- We should split the new_note stuff into its own form.
+ We should split the Edit form into a number of views for performing
+ actions on opportunities in Harvest. An opportunity should replace
+ “Edit” in its .actions element with links that directly carry out the
+ operations we need, without the user needing to load any more pages.
- Then, display more than one option in the actions area for each opportunity. For example, "Add note" and "Hide", each linking to a specific form.
- As an alternative (or in addition), the same link could go at the top of the opportunity-notes element.
+ For security and to make sure this works without Javascript, loading one
+ of those action views directly (without sending any POST data) should
+ lead (at least) to a confirmation form.
** Changed in: harvest
Assignee: (unassigned) => Dylan McCall (dylanmccall)
** Summary changed:
- Adding a note to an opportunity is not obvious
+ Split Edit form into individual actions for opportunities
--
Split Edit form into individual actions for opportunities
https://bugs.launchpad.net/bugs/618799
You received this bug notification because you are a member of harvest-
dev, which is the registrant for harvest.
Status in Harvest Service: Triaged
Bug description:
Right now, adding a note to an opportunity, setting a difficulty level or marking an opportunity Applied (see bug #581719) involves first knowing that the options exist, then navigating to the unclearly labelled “Edit” form.
We should split the Edit form into a number of views for performing actions on opportunities in Harvest. An opportunity should replace “Edit” in its .actions element with links that directly carry out the operations we need, without the user needing to load any more pages.
For security and to make sure this works without Javascript, loading one of those action views directly (without sending any POST data) should lead (at least) to a confirmation form.
References