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; } } }

JMWE: attachment field mandatory

Jurica Petricevic

Hi Community,

is this even possible?

When moving from the "open" status to the "in analysis" status, the attachment field should be mandatory, but if at least one has already been added during the "create" process, then no additional entry in this field is required.

Best regards

Jurica Petricevic

Accepted answers

Marcin Wiktor_9tk3n9

Hello @Jurica Petricevic

you can try to add a new validator to your workflow that requires "Attachment" field not to be empty Bez tytułu.png . To do such a thing, go to the "Workflows", "Edit" and then select that transition from "Open" to "In analysis" status and follow this screen:

David Fischer

Hi @Jurica Petricevic

you can use a "Scripted (Groovy)" Validator with this code:

issue.get("attachment") || getTransitionAttachments()

This requires JMWE 7.0.0 or higher.

Or you can use a Fields Required Validator (JMWE app) and use this Conditional Validation script:

!issue.get("attachment")

All comments

Marcin Wiktor_9tk3n9

Hello @Jurica Petricevic

Jurica Petricevic

@Marcin Wiktor thx for you time first of all.

Secondly, this does not solve my second part of the problem, where if there is already an attachment, the system ignores this field and releases the transition.

Bild 1.JPG Bild 2.JPG

David Fischer

Hi @Jurica Petricevic

you can use a "Scripted (Groovy)" Validator with this code:

issue.get("attachment") || getTransitionAttachments()

This requires JMWE 7.0.0 or higher.

Or you can use a Fields Required Validator (JMWE app) and use this Conditional Validation script:

!issue.get("attachment")

Carlos Faddul_kqcedv

@David Fischer does this script have differences to work in the cloud?
I have a similar business rule, to which it is necessary to attach the QA evidence in the transition to follow the process, however I could not even manage it via script or required field in validators.

David Fischer

@Carlos Faddul Jira Cloud works completely differently. Any workflow condition or validator must be written in Atlassian's Jira Expressions language.

What is your business requirement?

Carlos Faddul_kqcedv

@David Fischer in this case, in a transition screen, I need to force a new attachment to be attached, for QA evidence on the tests performed.
However I tried several ways, however it does not recognize when it attaches to the transition screen, only when it is in the issue view.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-software

jira-software-server

addon-com.innovalog.jmwe.jira-misc-workflow-extensions