Moving the Issue from one project to another and keep the reporter updated on the issues

[JS_GOK]

Hi, 

We have one project with default permission. This means any application login users can create issues/tasks etc in this project. Say, IT S/W General is the project. We got some to move this issue to appropriate Projets such as Web or Mobile etc.  These projects have different permission schemes, only assigned to S/W Team as a group. application login users do not have permission to this group. 

Now, general users open this IT  S/W General Project creates task, and it is working fine. And moving the task to a different project also works fine. However, as soon we move the project, it disappears from the general users' view and he can not see the updates to this task. 

We want to inform the reporter that it is moved to (say mobile) a different project and the status needs to show as well. 

What kind of permission do we need to give to the general users to see this?

Thanks

[Jack Brickey]

I recommend the following process/solution:

• do not move the issues, rather create a linked issue in the other project
• use automation to update the original issue based upon the new issue being updated. This can include things like comments (if desired), status, etc.

[reidt]

You could use unito.io to keep the projects constantly in sync, it would be more secure than changing the permissions.