xtriggers (graph view)

[oliver-sanders]

Add Xtriggers into the Graph View.

The Cylc7 Graph View has basic support for Xtriggers, the Cylc8 Graph View has a lot more potential.

We should provide special representations for Cylc Flow built-in xtriggers and some default representation for user defined Xtriggers.

Open questions:

• [x] Should Xtriggers disappear once satisfied? - No
  • Retry Xtriggers should, custom Xtriggers maybe not - Retry should remain visible
  • If not we could allow them to be reset from the GUI, see https://github.com/cylc/cylc-flow/issues/3221
  • If not we need a way to show whether an Xtrigger has been satisfied or not - Yes, use a tick or success icon of some form
• [x] Should queues use option (1) or (2) or something else? - Something else, use a badge in the same location as the held icon

[hjoliver]

Should queues use option (1) or (2) or something else?

Shouldn't be too messy if queue "triggers" are only shown when the task is actively held back - i.e. ready to submit as soon as released by the queue.

[oliver-sanders]

True, perhaps we should add logic to Cylc Flow for this special case.

However it is common to see suites (e.g. rose stem) where almost all tasks would be held back by a queue.

[oliver-sanders]

@hjoliver one for the workshop.

[oliver-sanders]

[cylc-con-2020]

• We are happy with this
• However, queues are special, they should appear next to the task icon in the space where the held modifier is located. The held badge should take priority, the queue secondarily.
• Xtriggers should remain after they succeed but their icon should be replaced with a tick or succeeded icon.