[#JRA-10814] Clone Projects

JIRA

Clone Projects

Created: 09/Aug/06 12:01 PM Updated: 25/Jun/08 09:41 AM

Component/s:

Project Management

Affects Version/s:

3.5.1

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Reference

This issue is related to:

JRA-7020 Allow support for project schemes or templates

~~JRA-14254~~ custom field "scheme" to help dealing with new project requests

Participants:	chuong, Jeff Turner [Atlassian], Kathy Fiffick, Martha Van Orshoven, Patrick Berry and Steve Isbell
Since last comment:	9 weeks, 2 days ago
Support reference count:	3
Labels:

Description

« Hide

Please add a feature that would allow JIRA to clone Projects.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Jeff Turner [Atlassian] added a comment - 09/Aug/06 07:35 PM

What would cloning projects involve?

Cloning just the project info (obviously the key would need to change)
Cloning associated permission, notification, workflow schemes?
Cloning associated custom fields?

What are the problems that you're experiencing, that you think project cloning will solve?

Cheers,
Jeff

[ Permlink | « Hide ]

Patrick Berry added a comment - 08/Sep/06 10:49 AM

We're starting to do a lot of rails programming. We create a project with a stock set of components and versions. Having a feature that just put those things in place would be great.

The three issues you mention do make things more complex though, so I can see why this is a hard thing to deal with.

[ Permlink | « Hide ]

Steve Isbell added a comment - 06/Aug/07 08:04 AM

We have been using JIRA for a while now and have many projects setup and requests for new projects coming in regularly from the project / dev teams. It would be really nice to be able to copy an entire project and its components, versions, associated workflow etc. So projects could be created rapidly.

[ Permlink | « Hide ]

Martha Van Orshoven added a comment - 11/Jun/08 02:54 PM

Hi,

It would be very valuable to me to be able to copy not only projects but components. It would save lots of time in manual keying in work.

[ Permlink | « Hide ]

Kathy Fiffick added a comment - 25/Jun/08 09:41 AM

We use JIRA for Change Request tracking with a very complex workflow. Since we are unable to prevent users from seeing select fields if they have the capability of browsing the project and its issues, I need the capability of cloning the entire project to another project in order to have a Public View project of all issues and their fields and an Internal View project of the same issues with sensitive proprietary attachments and comments.