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 set to empty ONLY when cloning ticket

Jeffrey Bistrong

I have been running into an issue recently where the reporter is being set to empty ONLY when cloning tickets.

This is happening in both the production and sandbox instance of jira. I raised this ticket with atlassian and so far they can't figure out what is causing the problem, so I figured I would post here to see if anyone else is running into this issue?

Accepted answers

All comments

John Funk

Hi Jeffrey,

That's strange. However, it says Anonymous for the Assignee, which is different from "Unassigned". How is the Reporter being populated in the original work item? What type of user is this - Jira licensed user, Customer, etc.?

Jeffrey Bistrong

fully licensed jira user with the appropriate create permissions on a project. once the ticket is cloned I am able to go to the ticket/reporter field and set it to the proper person.

John Funk

How are you doing the clone? Manually? Through automation?

Jeffrey Bistrong

manually, via the clone button from the hamburger menu drop down. and in sandbox no automation exists since it doesn't get copied down as part of the sandbox copy process

Jeffrey Bistrong

As a work around I put automation in place to set the value of the reporter from the issue.creator value. Monosnap Rule builder - Automation - Jira 2025-05-27 08-49-43.png

Clara Belin-Brosseau_Elements

Hi @Jeffrey Bistrong

As an alternative to Automation that can be really complex to implement and maintain sometimes, I can suggest trying our app Elements Copy & Sync to clone Jira issues with the fields that you need.

Any field can be easily cloned such as the reporter in your case.

map-reporter-to-assignee-copy-and-sync (1).png

More than that, you can also synchronize the issues together if needed so that if someone comments the source issue, the comments also appear in the clone issue. Synchronization can be one or two-ways.

Don't hesitate to check the documentation, it’s really quick and easy to set up.

The app is for free during 30 days (and it stays free under 10 users).

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud