nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Transition Condition based on content of custom field

Jason Gabbert

I have an issue with multiple people giving approval. The reviewers are selected in a custom field by the issue author. The individual approvals are then tracked in another custom field. I would like to put a condition on the transition to approved status when the custom field content includes all the selected reviewers.

I cant use {field_A} = {field_B} since the approvals may come in a random order. Ex:

Required Approvers: A, B, D, E

Approvals Recieved: D, B, E, A

should allow the transtion to approved status.

Tips?

Accepted answers

Boris Berenberg - Atlas Authority

What are your custom field types?

All comments

Boris Berenberg - Atlas Authority

What are your custom field types?

Jason Gabbert

Field A is a check box list, populated with selected initials. Field B is a text box with the same initials being appended. If I could force the approvals to come in in the same order as the field A selections, then the straight = would work, but the approvals can come in any order.

Jason Gabbert

I need the syntax to search: "is E anywhere in {field B}"

Boris Berenberg - Atlas Authority

Why not just use checkboxes for both? You're relying on issue history for auditing either way.

You may may consider using two user picker fields instead with transitions to approve into the second field. It makes it enforced by who users actually are, not just a trust that the change history will save you.