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: State of tasks not visible #15185

Closed
FlorianLudwig opened this issue Nov 13, 2019 · 9 comments
Closed

UX: State of tasks not visible #15185

FlorianLudwig opened this issue Nov 13, 2019 · 9 comments
Labels
area/plugins kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P1 Has a major impact to usage or development of the system.

Comments

@FlorianLudwig
Copy link

FlorianLudwig commented Nov 13, 2019

Is your enhancement related to a problem? Please describe.

It is not possible to see if a task is already running or a started task is done. This resulted in multiple issues for me:

  • First time i wanted to start a task I clicked on it - nothing happened so i tried double clicking. A few seconds later I had the task running three times.
  • I waited for a task to finish but didn't notice it was already finished since it there is no indication if a task is still running (I seem to have missed the notification)

Describe the solution you'd like

  • Make it visible on the right pane where tasks can be started if the task is already running
  • Create instant feedback when a task is clicked without waiting for the task to actually spawn server-side.
  • Make the task status visible in the tabbed bar itself, mockup:
    UX-che

Describe alternatives you've considered

  • Make it possible to declare tasks to be not possible to run concurrently (e.g. "install dependencies")

Environment / Steps to reproduce

  • Login to https://che.openshift.io/
  • Create new workspace
  • Use "Python Django" template
  • Wait
  • Click on the right side "box" icon: "My Workspace"
  • Click "install dependencies" (If it works after some delay a terminal opens - or if you clicked something else since you thought it didn't work, several terminals.)
@FlorianLudwig FlorianLudwig added the kind/enhancement A feature request - must adhere to the feature request template. label Nov 13, 2019
@benoitf
Copy link
Contributor

benoitf commented Nov 13, 2019

cc @RomanNikitenko

@benoitf benoitf added area/editor/theia Issues related to the che-theia IDE of Che severity/P2 Has a minor but important impact to the usage or development of the system. team/ide labels Nov 13, 2019
@benoitf benoitf added this to the Backlog - IDE 1 milestone Nov 13, 2019
@RomanNikitenko
Copy link
Member

@FlorianLudwig
is it some vs code extension on your screenshot?
could you share the reference for it, if so

thanks in advance!

@FlorianLudwig
Copy link
Author

@RomanNikitenko I used https://che.openshift.io/ and used an example/template there. I don't know if they have some special extensions there by default.

I updated the description with steps how to reproduce the issue.

@RomanNikitenko
Copy link
Member

@FlorianLudwig
Sorry, I asked you about the solution you'd like.

You provided this gif
UX-che

and I thought that you used some vs code extension for it.

@FlorianLudwig
Copy link
Author

@RomanNikitenko that was done using gimp ;)

@slemeur slemeur added severity/P1 Has a major impact to usage or development of the system. and removed severity/P2 Has a minor but important impact to the usage or development of the system. labels Nov 21, 2019
@slemeur
Copy link
Contributor

slemeur commented Nov 21, 2019

Thanks @FlorianLudwig for the proposal, it's a really good idea.

There are two sub-tasks for this issue:

  • 1. Displaying a small visual indicator about the state of a tasks. For this, I think proposal from @FlorianLudwig is perfect. I would just add that we could also add a tooltip on hover on the tasks output's tab saying the state of the tasks (ex: "{task_name} : RUNNING" or "{task_name} : COMPLETED") Mark in the task widget title when task is exited. #14132

  • 2. The delay between "the user clicks on the task" and "the output terminal is getting shown". This is the biggest issue IMO. The user doesn't really know if the action (clicking on the task) has been taken into account. When the connectivity is not great, this lead to very inconvenient UX. We should look at how we can first open the terminal output, so it gives a visual feedback to the end-user, display an indicator inside of it (ex: "Task "{task-name}" - Connecting....") and then do the necessary background connection between the task running in the container and the output displayed in the IDE Create instant feedback when a task is clicked without waiting for the task to actually spawn server-side. #15277

@vzhukovs
Copy link
Contributor

vzhukovs commented Dec 9, 2019

@slemeur there is a proposal to improve UX by adding information about flow which user perform to run task. Especially, when user clicks on the task in My Workspace - Che shows information in status bar that process preparing. Then, when terminal waits for the websocket connection show the loader in terminal tab. After that, when task finished Che will update icon in terminal tab to a success mark:

ux-openshift-io

@azatsarynnyy
Copy link
Member

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 21, 2020
@che-bot
Copy link
Contributor

che-bot commented Aug 21, 2020

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot closed this as completed Sep 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/plugins kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

7 participants