Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Update contact people edit form layout

Description

Overview: Editing contact people is cumbersome and hard to navigate. Field descriptions are repeated multiple times and there is a lot of wasted space. This can be confusing and intimidating for the user.

Acceptance criteria:

  •  

    • Given user is viewing a contact person

    • When clicking edit

    • Then the edit form displays address information at the bottom Check Mark

  •  

    • Given user is viewing a contact person Check Mark

    • When clicking edit

    • Then the edit form displays Email, Phone numbers and URLs in table layout
      See screenshot

Environment

None

Potential Workaround

None

Attachments

3
  • 10 Dec 2019, 03:59 PM
  • 09 Dec 2019, 10:12 PM
  • 25 Nov 2019, 06:43 PM

Checklist

hide

TestRail: Results

Activity

Show:

Dennis Bridges December 12, 2019 at 4:56 PM

There seems to be a problem with defined width of the buttons and trash can icon on the edit form. However I will create a separate bug for this.

Mikita Siadykh December 11, 2019 at 8:15 PM


please review primary buttons on testing env, thank you

Mikita Siadykh December 10, 2019 at 5:44 PM

agreed for checkboxes -> buttons

Might need to split it up for each app? we can start with 1 and discuss on grooming

Dennis Bridges December 10, 2019 at 5:39 PM
Edited

Thanks and I will define a separate UX story for repeatable field headings. Might need to split it up for each app?
However, as per Kimie's request we should implement the buttons instead of using checkboxes. thx!

Mikita Siadykh December 10, 2019 at 4:30 PM

hi

it's 100% true we should keep layout as clean as possible, but it shouldn't impact UX and accessibility (there is a practice to work with form controls without visible labels, it's not a problem, but requires effort), if you think it's ok from UX side (not UI) than I'd suggest to create new story to update our repeatable fields with one heading as we need common way to do this (we can't reuse what's done for inventory)

Done

Details

Assignee

Reporter

Tester Assignee

Labels

Priority

Story Points

Sprint

Development Team

Thunderjet

Parent

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created November 25, 2019 at 6:44 PM
Updated December 30, 2019 at 12:17 PM
Resolved December 12, 2019 at 4:56 PM
TestRail: Cases
TestRail: Runs

Flag notifications