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

Reporter to change when cloning a ticket

soren nielsen_q67934

How does this work when you CLONE and issue..

The person who clones is different than the originator of the ticket.. how do I get the NEW CLONED ticket to have the person that cloned it as the REPORTER - I do not want the original ticket creator as the reporter..

Accepted answers

All comments

Brant Schroeder

@soren nielsen The clone issue process actually clones the issue so there is no way to change the reporter until after the issue is cloned. You could use automation to change the reporter. I think this should work.

Screenshot 2022-09-20 151006.png

You might want to put some additional parameters in your JQL to limit it to a specific issue type, etc.

soren nielsen_q67934

That sounds great, can I do this on the server version? or is this only for cloud?

Brant Schroeder

@soren nielsen my example was cloud. There is automation on server and it should work the same there.

Niki Wennink

I have the same question, but the above example is not possible. It is possible to set the assignee to the issue creator, but not the reporter. How can I do that?

Niki Wennink

To set the reporter of the newly cloned ticket to the issue creator (the person who cloned) I did the following:

In the advanced part of the then statement I added this code:

{
    "fields": {
        "reporter": { "id": "{{initiator.accountId}}" }
    }
}

This automatically changed the reporter of the cloned issue for me.

James Fama_loxex6

Hi Atlassian community,

The above method did not work for me.

The following method works for me. The first two steps are the same except for the last steps. We did this following:

Screenshot 2024-01-30 at 10.17.37.png

Screenshot 2024-01-30 at 10.19.47.png

Screenshot 2024-01-30 at 10.20.54.png

Matthew Martin

I see you've all implemented a solution here to change the reporter. I wanted to know, does this resolve the problem of a "Create issue" notification going to the original reporter who I assume is still briefly assigned before A4J jumps in and changes the reporter?

Welcome!

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

Quick Links

Find more posts tagged with

jira-service-desk-server

atl-gruland

jira-service-management

jira-service-management-server