Differentiate AEM DEV related JIRA tasks that include JUnit or Jest testing.

[Jeetendrakumar Sahu]

To enforce a process where AEM DEV JIRA tasks must include either a JUnit or Jest label before they can be closed, Need a JIRA custom fields, validation rules, and workflow conditions, please suggest.

[Jorge Cammarota]

If you don't have access to the workflow (Cloud Free/Standard), use Automation:

Rule:

Trigger → “Issue transitioned”

From: any status

To: Done/Closed

Condition:

Issue Fields → Labels

Contains JUnit OR Jest

Action (if NOT match) →

Transition issue back to the previous status

Add comment:

"To complete AEM DEV tasks, add the JUnit or Jest label."

Flow:

If the developer tries to close --> rule validates --> if there are no tests, it blocks and returns with a warning.