Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Configuring Issue Collectors so that the Reporter is the Submitter?


I'm trying to figure out if there's a way to link the user that submits a Jira intake issue from a web-based issue collector to the reporter field in Jira. Currently, we have the Name, Email, Submitter Name, and a unique identifier in the issue collector form. Is there a way through automation or the configuration of the collector itself to assign the reporter as the user who submitted the ticket?

Appreciate any help on this!

1 answer

0 votes
Brant Schroeder
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 04, 2023

@Krista Nicol The short answer is no.  The reason is that a reporter needs to be a licensed user in Jira.  When someone submits the issue collector they can be anyone and in order to make this work you would need to use an app that would allow you to create a user in Jira and provide them with a license when the issue is created and then assign them as a reporter after that is done.  You can do it technically but you would be giving random individuals access to your Jira instance.   The better way to go is to use Jira Service Management and use automations to create issues in your software instance and link them together.  

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events