Why when i move a an epic from one project to another does the reporter change?

We have an epic listed in a subtending backlog. Once its approved we move it from the subtending backlog to the master backlog. It appears that occassionally the person in reporter role is changed when the epic is moved from one project to the other. Any ideas why I am seeing this happen?

3 answers

1 accepted

This widget could not be displayed.

One other thing that you might check is the conditions setup in the workflow transitions. Sometimes if you use default, JIRA might have conditions like "Only users with Create issues" permissions can execute this transition etc. If you have different workflows setup for different issue types and they have different conditions, that might be the case.

I see nothing in the logs, and yes i have that condition set, but the users do have te permissions to create issues too.

Can you verify the following:

  1. When you move, you are using the "more>move" option in the issue itself?
  2. You have seen that if project admin follows the process at #1, there have been cases where the reporter was either the admin or it stayed the same?
  3. This issue happens for the same issue type or different issue types?
  4. If different issue types, do they have same or different workflows?
  5. If different workflows, are the conditions for create issue transitions are the same?
  6. Do the workflows have custom post functions?
  7. If so, what are those?

Overall, what you are seeing might be caused by:

  • Worfkflow conditions
  • Workflow post functions

that are related to create issue step.

One last thing I can think of is the database integrity (assuming you are not using HSQL) and/or indexing.

If all look OK above, I would definitely create a support ticket.

This widget could not be displayed.
Whoever moves the ticket to the new project would be the reporter as the mover technically is creating that ticket in the new project by keeping other values. If you want to keep that record, you could add a user custom field copy the original reporter in the workflow then copy that back once create the ticket in the other project workflow.

I would typically agree with that but that doesn't seem to be the case all of the time. It seems when i move them as a super admin it doesn't change or and it only changes some of the time when the project admin moves tem. I haven't been able to nail down the situation when it changes and when it doesn't.

And do you see anything in the logs?

This widget could not be displayed.

I would typically agree with that but that doesn't seem to be the case all of the time. It seems when i move them as a super admin it doesn't change or and it only changes some of the time when the project admin moves tem. I haven't been able to nail down the situation when it changes and when it doesn't.

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted Wednesday in New to Jira

Are you planning to trial, or are currently trialling Jira Software? - We want to talk to you!

Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in   talking to 20 people planning t...

85 views 1 0
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you