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.

Sign up for GitHub

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

Jump to bottom

Workspace panel is not getting update with newly added task #13666

Open
slemeur opened this issue Jul 2, 2019 · 3 comments
Open

Workspace panel is not getting update with newly added task #13666

slemeur opened this issue Jul 2, 2019 · 3 comments
Labels
area/plugins kind/bug Outline of a bug - must adhere to the bug report template. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P1 Has a major impact to usage or development of the system.
Milestone
7.x (Later, Futur...

Comments

@slemeur
Copy link
Contributor

slemeur commented Jul 2, 2019

Description

When adding a new task, the task is not getting visible into the workspace panel.

Capture d’écran 2019-07-02 à 11 51 20

Reproduction Steps

  • Create a workspace with nodejs and a sample project
  • Open the menu "Terminal" and then "Configure Tasks"
  • Add a new task in the tasks.json
  • Check the changes in the workspace panel --> Nothing
  • Refresh the IDE and check if the tasks is getting listed now --> Nothing

OS and version:
Che 7.0.0 RC3
chectl minikube
@slemeur slemeur added kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. team/ide2 labels Jul 2, 2019
@sunix
Copy link
Contributor

sunix commented Sep 18, 2019

@vparfonov is this ide1 issue ?

@slemeur slemeur mentioned this issue Oct 16, 2019
Closed
@l0rd l0rd mentioned this issue Oct 16, 2019
Open
15 tasks
@ericwill ericwill mentioned this issue Jul 15, 2020
Closed
38 tasks
@ericwill ericwill added this to the 7.17 milestone Jul 15, 2020
@sunix
Copy link
Contributor

sunix commented Jul 17, 2020 •
edited
Loading

In my opinion, users should have a way to edit actions/task in the current devfile and have them updated.
I would rather work on #13983 maybe

@che-bot
Copy link
Contributor

che-bot commented Feb 4, 2021

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 added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 4, 2021
@sunix sunix added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/plugins kind/bug Outline of a bug - must adhere to the bug report template. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Milestone
7.x (Later, Future, Never)
Development

No branches or pull requests
5 participants
@sunix @azatsarynnyy @slemeur @ericwill @che-bot