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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

The Name and Email fields in issue collectors are not stored in the issue details

Hi all,

I've recently set up an issue collector for the first time - absolutely love it. I do have a problem though and I was wondering if anyone knew the answer.

By default there is a Name and Email field on the form and that's exactly what we need as the end users do not have JIRA accounts. Unfortunately the information they put in to these fields does not seem to display on the resulting JIRA issue.

Does anyone know how you can get that information in there?

Off the back of that, these fields seem to be optional - anyway to make them mandatory?

Thanks in advance,


3 answers

1 accepted

0 votes
Answer accepted

I've worked it out! The Name and Email fields drop their content in to the Description Field.

However, the screen used for issue creation didn't have the Description field present (it was on the View screen). I added it to the Creation screen and it now displaying the contents of those fields!! HURRAH!!!

Thank you for the answer to this!

Is it not present in the Description at the end?

It is not, no.

Any other ideas? This is basically stopping us using this feature - it's used within our internal tool where it's critical we know who's raised the bugs but we haven't got enough licenses to add all the end users to JIRA.

@Renjith [Atlassian] How can the value of the email be searched for within the Description field to maybe a custom scripted field, so that value can be emailed on status changes of the ticket?

Does anyone have any other ideas on this subject? It sounds like it should just work but it doesn't.

Possible something to do with workflow?

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you