Uploaded image for project: 'DESIGN'
  1. DESIGN
  2. DESIGN-448

Iterate solutions for complex metadata

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Minor
    • Resolution: Done
    • Component/s: Ergonomy & UX
    • Epic Link:
    • Tags:
    • Team:
      GANG
    • Sprint:
      nxGang Sprint 11.1.20, nxGang Sprint 11.1.21, nxGang Sprint 11.1.22, nxGang Sprint 11.1.23, nxGang Sprint 11.1.24, nxGang Sprint 11.1.25, nxGang Sprint 11.1.26, nxGang Sprint 11.1.27, nxGang Sprint 11.1.28
    • Story Points:
      0

      Attachments

        Issue Links

        is related to

        User story - Created by Jira Software - do not edit or delete. Issue type for a user story. NXP-28487 as a user, I can easily "expand/collapse" search facets when there are "numerous" fields/facets to choose from

        • Major - Major loss of function.
        • Resolved

        Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. NXP-28486 addressing specific UX issues on search with large amounts of metadata

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Open

        Task - A task that needs to be done. DESIGN-410 Mockup possible solutions for layouts with complex metadata

        • Major - Major loss of function.
        • Resolved
        is required by

        Sub-task - The sub-task of the issue DESIGN-526 Complex Metadata - Write Design Guidelines for implementation

        • Major - Major loss of function.
        • Resolved
        mentioned in

        Page Loading...

          Activity

            People

            • Assignee:
              cgouveia Carolina Gouveia
              Reporter:
              cgouveia Carolina Gouveia
              Participants:
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 2 weeks, 2 days
                2w 2d