Project

General

Profile

Actions

Feature #17499

open

Issues Do Not Copy when Issue Tracker is Disabled from "Copy From" Project

Added by James H over 10 years ago. Updated over 10 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Issues planning
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:

Description

We use a template project and copy projects every time we initialize a new project.

We would like to use the copy function to be able to copy over all entities of the copy from project, regardless of whether or not the entity is "disabled".
Additionally, in regards to issues in particular, we also need to be able to "update" or "edit" the issue in the project that has that particular issue tracker disabled.

Currently, when we copy from our template project, issues that have the tracker disabled for our template project do not get copied over. Even if they did, we cannot "update" or "edit" those issues because upon "edit"ing, the tracker defaults to the first available tracker (and displays custom fields in relation to the first available tracker).

We use this method because we need certain issue-types available in the project while not allowing users to create new issues of that tracker type.

This could also be solved with visibility/use-ability settings for issue trackers per role per project.


Related issues

Related to Redmine - Defect #17211: Assigning Parent Project when Copying ProjectClosed

Actions
Related to Redmine - Feature #17500: Visibility/Use-ability/Creation Settings for Issue Trackers per Role per Project.New

Actions
Actions

Also available in: Atom PDF