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

ScriptRunner for forcing attachment

Hadas Hamerovv

Hi,

I've installed ScriptRunner and now wish to force attachment (PRD) whenever a new feature is moved to development.

since validators won't perform best I thought the way to perform this is by adding post function that makes the attachment mandatory when moving the item to the 'Requirements' status.

If I understand the way things work this will force from this stage on to add an attachment. So in the next step (moving to development) the Product team will have to attach the file.

Hopefully once the file is there the system will not force another attachment again and again.

The problem is I have no clue for how to write this script in the post functions.

Can someone help or advise a better way to force adding the PRD document before transitioning the issue to the developers?

Accepted answers

Nic Brough -Adaptavist-

Ok, take a step back:

This is something you should be doing with a validator. A post-function is completely and utterly the wrong place to do validation. Post-functions do things when a transition is confirmed and have no way to go back to a user and say "no, this is wrong". It's too late to go back by the time you reach the post-functions. The only way they can stop the transition is to throw a horrible error and possibly leave your issue in an inconsistent state.

This sort of checking is exactly what validators are for. What makes you think "validators won't perform best"? (Not that it really matters how they perform, as they are the only place you can actually do this)

All comments

Nic Brough -Adaptavist-

Ok, take a step back:

Hadas Hamerovv

Everything you said is correct but notice that I am adding a post function on a prior transition.

So when the issue is in the new status and onwards the field is mandatory.

I don’t see why won’t that work. My problem though is I don’t yet understand how to write the scriptrunner code.

Nic Brough -Adaptavist-

Again, do not do that.

A post-function is the wrong place to try to do this. Do it in a validator.

It won't work because post-functions are not the place to do validation and they do not support it.

Hadas Hamerovv

But I am not doing validation Nic. I just make the field mandatory from a certain point onwards.

I don't see why this approach won't work.

Here are the steps for example:

1. issue is open.

2. Issue is moved to 'in progress' (A post function on this transition makes the attachment field mandatory)

3. Issue needs to be moved to done and now the field is mandatory so cannot be done unless there is an attachment.

Welcome!

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

Quick Links

Find more posts tagged with

scriptrunner

jira-cloud

jira-core