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

Feathr UI feedback #272

Closed
15 of 22 tasks
blrchen opened this issue May 18, 2022 · 6 comments · Fixed by #491 or #455
Closed
15 of 22 tasks

Feathr UI feedback #272

blrchen opened this issue May 18, 2022 · 6 comments · Fixed by #491 or #455
Assignees
Labels
help wanted Extra attention is needed

Comments

@blrchen
Copy link
Collaborator

blrchen commented May 18, 2022

This issue is opened for tracking feedbacks received for Feathr UI so far

Preview site

https://brave-moss-045d2ce00.1.azurestaticapps.net

Feedbacks

  • Display feature key in details page
  • Have a quick start (preview mode)
  • Add a summary homepage
  • The project that this person has worked on or browsed
  • Or biggest/most popular project if this person has worked on no projects
  • Add an Avatar with name initials on the right near the logout button
  • Put a “Under construction” sign for jobs page
  • Add a feature monitoring page and add “Under construction” sign
  • [Lineage] Highlight the feature I clicked
  • [Lineage] Color the features in the same project as this feature with one color. And the other projects with different color. Also add color encoding illustrations
  • [Lineage] Embed the page in the feature sub tab
  • [Lineage] Remove unused Lineage (i.e. Atlas Process) in the UI
  • [Lineage] When click on the lineage blocks, jump to the corresponding feature page
  • [Lineage] After i clicked a certain figure, can we highlight the feature where i clicked?
  • [Lineage] Slightly move the graph in the middle.
  • [Lineage] Add tooltip or explanation text for what each color means
  • [Lineage] Add a way to click the feature and open the detail page.
  • For source page, display the projects that this person has worked on
  • For feature page, display the projects that this person has worked on
  • Make the search bar work
  • Show the “tag” part
  • Show the users who updated the feature, and what’s the updated time
  • All the contents in the feature page (like here)
  • Source should be clickable and have its own page like features. The source page should display all features belong to this source of a project.
@hangfei
Copy link
Collaborator

hangfei commented May 18, 2022

Could we add: source should be clickable and have its own page like features. The source page should display all features belong to this source of a project.

@xiaoyongzhu
Copy link
Member

Can we also add this one?

  • Remove unused Lineage (i.e. Atlas Process) in the UI

@blrchen blrchen added the help wanted Extra attention is needed label May 19, 2022
@blrchen
Copy link
Collaborator Author

blrchen commented May 19, 2022

Could we add: source should be clickable and have its own page like features. The source page should display all features belong to this source of a project.

Thanks for feedback, this has been appended to the list in description.

@blrchen
Copy link
Collaborator Author

blrchen commented May 19, 2022

Can we also add this one?

  • Remove unused Lineage (i.e. Atlas Process) in the UI

Thanks for feedback, this has been appended to the list in description.

@xiaoyongzhu
Copy link
Member

Consider adding metadata health and owners information

blrchen added a commit that referenced this issue Jun 2, 2022
This PR update ui code to align with latest api spec which abstracts common interfaces among different registration providers. This PR also enhances lineage ux experience and adds RBAC experience for flighting.

New Feature registration API integration
API spec can be viewed at https://feathr-registry.azurewebsites.net/docs. UI code is now purview free.

UX improvements
 When a feature is clicked, the feature node is highlighted
 When a feature is clicked, the feature level lineage path is highlighted. Feature level lineage means direct producer and consumer.
 Nodes in graph are colored grouped by feature type.
 User can toggle graph to filter by feature type.
 Flow arrow is enabled to indicate producer and consumer relationship
 All out of scope resources are removed in graph, for example, Altas Process, Project.
 Add navigate button in node so user can click to navigate to feature detail page.
 RBAC in flgihting, accessible via /management path.

Linked issue: #272
@blrchen blrchen pinned this issue Jul 21, 2022
@blrchen blrchen unpinned this issue Jul 21, 2022
@blrchen
Copy link
Collaborator Author

blrchen commented Jul 21, 2022

Closing this long UI MVP feedback list as most of them are already addressed.

For remaining uncompleted items, new issues are opened for tracking separately.

@blrchen blrchen closed this as completed Jul 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
3 participants