I am replacing a developer with another one and need to migrate the issues the old developer was working on to a new developer. Then I want to delete the old developer. Can this be done in Jira On Demand?
Hi Mike,
Make sure you have removed from your project's workflow a property on the Closed step that does not allow editing closed issues. That might be why you cannot change your assignee and reporter.
Hope this helps.
Regards,
Marlon
Hi, just in case check if you have the Bulk Change global permission.
Another thing, if I remember correctly you have to check if the fields are in the Edit Screen for that issue type.
And to take note, you can assign the issues to the new developer and then erase the old developer from the jira-users group. If he isn't on the group it won't be able to login and it won't count on Jira's User License.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What you'll do first is change the assignee and reporter to yourself. Then you would disable the user account. And if you feel confortable, you can then delete the user.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Or go straight to the new developer if you can - it's a bit quicker.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My problem is that I can't bulk edit the assignee or reporter. It says I either don't have permission or that one of the issues doesn't permit editing. I am the admin, so I should have permission and these are normal issues, shouldn't be any reason we can't reassign them.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you are migrating old issues (ones that have already been closed), then do you have your workflow set up so that you can't edit a closed issue? If so, then that is probably why it is not allowing you to edit the assignee/reporter. Easiest solution in this case might be to remove the restriction from the workflow (its a jira-editable property). Do the migration. Put the restriction back on the workflow.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.