History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: JRA-750
Type: New Feature New Feature
Status: Closed Closed
Resolution: Fixed
Priority: Minor Minor
Assignee: Scott Farquhar [Atlassian]
Reporter: Sebastiano Pilla
Votes: 5
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
JIRA

Move issues between projects

Created: 03/Sep/02 04:13 AM   Updated: 09/Apr/03 09:21 AM
Component/s: None
Affects Version/s: None
Fix Version/s: 2.0

Time Tracking:
Not Specified

Issue Links:
Duplicate
 

Participants: david valentine, Mike Roberts, Scott Farquhar [Atlassian], Sebastiano Pilla and Wolfgang Tank
Since last comment: 285 weeks, 4 days ago
Resolution Date: 28/Jan/03 07:01 PM
Labels:


 Description  « Hide
When trying JIRA, a number of users with access to more than one project have created issues in the wrong project. We would therefore like to have the possibility of moving issues between projects, along with attachments.

I'm thinking about a new permission, named "Move Issues": this permission could be assigned to the jira-administrators group. When an user in the jira-administrators group would view an issue's detail, she would also have a button named "Move Issue": clicking this button would lead to a form with a drop-down menu of projects and a Confirm button. Clicking the Confirm button would essentially create a new issue in the destination project and delete the issue in the original project.

The new issue in the destination project could have sensible defaults, such as Components = None and Version = None; attachments should be moved also, from the directory of the original project to the directory of the destination project.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Scott Farquhar [Atlassian] - 03/Sep/02 03:24 PM
Also see JRA-631 for more information.

Mike Roberts - 27/Sep/02 04:05 AM
I'd like this too. The department I'm in has several projects, and I've also setup a Jira project called 'New projects' where external users can make requests for entirely new projects.

If 'move issue to project' was available, when we created a new Jira project based on a request in the 'New Projects' Jira project, we could then move the request to the new project.

Hmmm, kind of a tongue twister this one....


david valentine - 22/Oct/02 09:10 AM
Move is ok, but it would be better to "Move/copy issue to new project". The options would be "Move (copy, resolve, and close)" or just "Copy"

Wolfgang Tank - 01/Nov/02 02:15 AM
yes, copy would be good. Our customer wants to track an issue in different projects.

wt


Scott Farquhar [Atlassian] - 28/Jan/03 07:01 PM
This is fixed in EAP 7.0.

You will need to add people to the 'move' permission for this to happen.

Thanks for the report!