プロジェクト

全般

プロフィール

Vote #75407

未完了

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

Admin Redmine さんが約4年前に追加. 約4年前に更新.

ステータス:
New
優先度:
通常
担当者:
-
カテゴリ:
Issues planning_40
対象バージョン:
-
開始日:
2022/05/09
期日:
進捗率:

0%

予定工数:
category_id:
40
version_id:
0
issue_org_id:
17499
author_id:
94920
assigned_to_id:
0
comments:
3
status_id:
1
tracker_id:
2
plus1:
0
affected_version:
closed_on:
affected_version_id:
ステータス-->[New]

説明

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.


journals

Sort of related to #17500
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------


related_issues

relates,Closed,17211,Assigning Parent Project when Copying Project
relates,New,17500,Visibility/Use-ability/Creation Settings for Issue Trackers per Role per Project.

Admin Redmine さんが約4年前に更新

  • カテゴリIssues planning_40 にセット

他の形式にエクスポート: Atom PDF

いいね!0
いいね!0