Scheduled executions should have a "scheduled" state (not running) until they are started

Bug #1641968 reported by Dougal Matthews
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mistral
Invalid
Medium
Dougal Matthews

Bug Description

At the moment if you create several executions they will all have the state "RUNNING" so it isn't clear which are waiting and which have actually started.

We should set them to a "SCHEDULED" or waiting state until they start. Then they are "RUNNING"

Dougal Matthews (d0ugal)
Changed in mistral:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.