Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UX improvement for dialog for initiating a transfer (Consumer) #709

Open
tmberthold opened this issue Mar 22, 2024 · 0 comments
Open

UX improvement for dialog for initiating a transfer (Consumer) #709

tmberthold opened this issue Mar 22, 2024 · 0 comments
Assignees
Labels
clean-backlog requires backlog cleaning kind/enhancement New feature or request

Comments

@tmberthold
Copy link
Member

Feature Request

Description

As a Consumer who initiates a data-transfer, I want to not get confused by the dialog, so I can distinguish and understand which information is for the data-sink and which for the data-source.

Which Areas Would Be Affected?

EDC-UI

Why Is the Feature Desired?

Currently it sometimes leads to confusion internally and also for the customer in the dialog for initiating the data-transfer as to which information belongs to what, as this is not visually separated, only by a heading and you actually have to implicitly already know the meaning of the fields to be sure.

How does this tie into our current product?

UX improvement

Stakeholders

UI-users

Solution Proposal and Work Breakdown

You could use the same structure here in this dialog as when creating an asset, with steps 1, 2 and 3, here then just "1 Data-Sink" and "2 Data-Source" if the Provider has switched on parameterization.

image

@tmberthold tmberthold added the kind/enhancement New feature or request label Mar 22, 2024
@AbdullahMuk AbdullahMuk self-assigned this May 1, 2024
@AbdullahMuk AbdullahMuk added the clean-backlog requires backlog cleaning label May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clean-backlog requires backlog cleaning kind/enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants