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

Removing Reporter from Cloned issues

Dan_g2zio1

Hi All!

Hoping someone is able to assist with this!

We are trying to remove (clear field) of the 'Reporter' field when an issue is cloned.

** The goal here is to prevent emails from sending to a reporter when the issue is cloned **

Has anyone been able to do so with ScriptRunner / JMWE post functions? I don't see as much information online when looking around (was hoping to come across a template to modify)

Any helps is appreciated! Thank you in advance!

Daniel

Accepted answers

David Fischer

Hi @Dan ,

as far as I know, only Jira Service Management issues can have no Reporter. In Jira Software, if you try to clear the reporter field (manually), you get an error.

However, using JMWE, you can actually clear the Reporter field with a Clear Fields post-function.

Therefore, what you can do is add a Clear Fields post-function to the Create transition, and use this conditional execution script:

!!issue.key

All comments

Trudy P Claspill

I believe that Reporter may be a required field in all issues, so I don't think you can "clear" the field. You are going to have to have some valid user specified as the Reporter, I think.

I'm not aware of a way to override the built in Clone function to change the setting of the Reporter field. You might be able to build something the the Automation feature that triggers for Issue Created and has a condition around "issue has a 'clones' link", and then change the Report field for such issues immediately after creation.

David Fischer

Hi @Dan ,

as far as I know, only Jira Service Management issues can have no Reporter. In Jira Software, if you try to clear the reporter field (manually), you get an error.

However, using JMWE, you can actually clear the Reporter field with a Clear Fields post-function.

Therefore, what you can do is add a Clear Fields post-function to the Create transition, and use this conditional execution script:

!!issue.key

Dan_g2zio1

Hi Trudy!

Thank you for your response!

I have tried project automation and it does work, but it does not solve our goal in which we do not want the reporter to receive a "issue created" email when cloning an issue (which is why we are trying to remove them before the email can be triggered for the cloned issue).

Thanks!

Daniel

Dan_g2zio1

Hi @David Fischer .

Thank you for your response!

I have tried to clear it - which in theory works with JMWE, but the only problem is we only wish to remove / replace the reporter when cloning an issue.

The goal is to not have an email go out to the reporter when our staff clones an issue (which is why I believe if we remove / replace the reporter on Cloned issues before the trigger post function, it should not send an email to the reporter) - at least in theory.

Would you know of a way to accomplish this?

Thank you!

Daniel

David Fischer

Hi @Dan ,

that's exactly what I offered - the Conditional Execution script for the Clear Fields post-function will make sure the Reporter is only cleared during a Clone operation.

Dan_g2zio1

Oh my @David Fischer

Apologies! I didn't think that one line would have completed it for me. Just tested it and it seems to work.

Thank you so much and have a great weekend!!!

Daniel

Welcome!

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

Quick Links

Find more posts tagged with

server

scriptrunner

jira-software

jira-software-server

groovy

issue-link

link

clone