We need to import Epic data into JPD as Ideas (in mass quantities) and want the creator of the Epic to be the creator of the Idea in JPD. It is likely our Atlassian Admins will be doing this activity and we definitely do not want JPD Ideas creator showing as our Atlassian Admins
We would like the ability to map the Epic Creator to the Idea Creator in JPD
Is there anyway around this or is it being considered by Atlassian JPD Team?
@Eileen McEneaney it doesn't appear to be possible to change the creator, you could try a workaround such as creating a Reporter field in JPD and copying the Reporter from the epic to the JPD Reporter field
Atlassian Team members are employees working across the company in a wide variety of roles.
June 12, 2024 edited
Hi Eileen,
If you Move an epic to a Jira Product Discovery project, the original creator will remain, however most of the other information will be lost.
If you want to use this option I'd suggest taking advantage of global fields/custom fields: If you have custom_fieldA in your Jira Software project, don't create a new_project_field_B in your Jira Product Discovery project.
Instead, reuse and add custom_field_A in your Jira Product Discovery project. When moving an Epic to a Jira Product Discovery project, the value will be kept.
If you export your Epics, and then import them, then you might want to use the "reporter" field to get this information, as the creator will be the admin performing the migration, but the Reporter can be set as the original creator, as mentioned by @Stephen_Lugton
Best Regards, Hermance Product Manager @ Jira Product Discovery
Thanks Hermance for your reply. We don't want to move the Epics, we want to copy Lean Business Case fields from our Epics to a JPD idea and we don't want to give the impression that an Atlassian Admin is the creator of the idea. We differentiate between creators and reporters on issues here so its a bit of a bummer that the creator of the epic won't be seen as the creator of the idea in JPD. But if that is the way it works we'll figure out a way to communicate that internally and rethink.
If Atlassian decides to change this going forward that would be ideal.
