Is your feature request related to a problem? Please describe.

Porting the collapsible sections from Custom Options to Conditions makes sense, but Custom Options have the benefit of a descriptive name (set by the user in Author Mode). Conditions are not labeled beyond their index, so these are "Condition 1" and "Condition 2" and so forth.

If you collapse multiple conditions, you have to expand them all again to differentiate them.

Describe the solution you'd like

Use the condition's values to confabulate a descriptive name, if possible.

In this case, instead of Condition 1 when collapsed, you could generate:

1. If Trigger 1 Active Is True Then...

...and display this rather than just Condition 1. Obviously, more complicated conditions could potentially get very long names, but an abbreviation of the first condition is probably sufficient for most users.

Describe alternatives you've considered

Whining at Rivers in Discord while he repeats "submit a ticket" over and over again.

Additional context

No.

This is very close to #705 and was solved with #4495

Whining at Rivers in Discord while he repeats "submit a ticket" over and over again.

rude

For seriousness, though, there is a potential issue with localization for auto-generated names. It's non-trivial to translate "If X is Y then do Z" into other languages, and still retain enough flexibility to describe "most" conditions.

Yeah, it's a consideration, but it seems like it would be effectively no different from how the fields used to enter data are organized, so that translation would be no better or worse than what the UI does for an expanded condition.

Well to nitpick, the word "is" does not appear anywhere in the Conditions UI, so 1. If Trigger 1 Active Is True Then... would not correspond with that suggestion. But sure, that makes sense.

1. If Trigger 1 Active = True Then...
1. If Trigger 1 Active (True) Then...

But yeah, your point stands.

Also Trigger 1 might not be a very descriptive name as #705 points out.