UX: When making a job when: delayed; change the UI after expire time of start_in

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Summary

I have created a job, which will announce a release using the Release API.

I've set the announcement to:

job:
  when: delayed
  start_in: 86 minutes
  script: anounce_release

This works great. However after the job has successfully run, the 'play' button is still there, and running the job again fails of course (can only do 1 release with the same tag). The confusion arouse because of the 'play' button with the 'manual' hover text, indicating the job is ready to run or needs some extra action.

What is the expected correct behavior?

I think that if the job has run its successful course, it should change its UI elements to a normal job element, indicating no manual course is needed. Only a replay button would be available, as per normal.

Relevant logs and/or screenshots

Note that the red cross is from me pressing the button again, before it was green, with of course the same wrong UI element as to the right.

Likewise, if the entire pipeline is cancled, I don't expect to see the [>] play button there either.

Possible fixes

After the delayed timer has expired, change the UI element to a normal job one.