Re: Problem with bulk move

"Pitt, Joseph" <[email protected]>
Newsgroups gmane.comp.java.jira.user
Message-ID <[email protected]>
It's been a while since I moved an issue. We don't allow it on the account I'm currently on. However I think it is asking for a reporter in case one of the issues' reporter isn't available in the new project.
 
Joseph (Joe) Pitt
Senior Member of Professional Staff
SRA International, Inc.
[email protected] 
443-624-5063

________________________________

From: [email protected] on behalf of [email protected]
Sent: Sun 6/26/2011 1:59 PM
To: [email protected]
Subject: [JIRA-user] Problem with bulk move



Hi,
I have a problem when bulk moving defects from one project to another.
JIRA asks me to enter a reporter in the destination project. So, I tried to check for which defects I have to give the information. I found hundreds of them.
I checked for one defect : this defect has a reporter. This reporter is allowed to create defects in both projects. But when I move this defect using the bulk moved feature, I first give the destination project and type and then a new screen appears, asking me to enter a reporter.
I don't understand why JIRA is not able to map the reporter...
This is a big problem for me. I don't want to loose the information on the reporter, and I have 1500 issues to move.
What shall I do to be able to migrate the issues and keep the reporter info?

Thanks
Stéphane
--
Post by jiraddict - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=54983
_______________________________________________
Jira-user mailing list
[email protected]
To unsubscribe or change your options visit this page:
http://lists.atlassian.com/mailman/listinfo/jira-user

_______________________________________________
Jira-user mailing list
[email protected]
To unsubscribe or change your options visit this page:
http://lists.atlassian.com/mailman/listinfo/jira-user
winmail.dat (application/ms-tnef, 4.5 KB) - not displayed
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.