プロジェクト

全般

プロフィール

Vote #66452

未完了

Add copy project permission

Admin Redmine さんが7ヶ月前に追加. 7ヶ月前に更新.

ステータス:
New
優先度:
通常
担当者:
-
カテゴリ:
Projects_11
開始日:
2010/01/29
期日:
進捗率:

0%

予定工数:
category_id:
11
version_id:
32
issue_org_id:
4687
author_id:
5349
assigned_to_id:
0
comments:
32
status_id:
1
tracker_id:
2
plus1:
13
affected_version:
closed_on:
affected_version_id:
ステータス-->[New]

説明

With the ability to copy projects, it would be nice to be able to grant permissions to do so. Currently only Redmine administrators can copy projects. If this permission is added a Copy project link could be added on the Overview tab next to the Add subject link.


journals

I 2nd this, this feature would be very nice to have. If someone has permission to be able to create a project they should be able to copy one.
--------------------------------------------------------------------------------
In my version (0.8.4.stable.2777), only administrators can create new projects. If the latest version allows permission grant to non-Administrators for creating new projects then the request makes sense. I will suggest the following logic to allow project copy to an individual:

*if (__user is allowed to create new a projects__) AND (__user is a manager or something equivalent for this project__) then user can copy this project*

This will ensure that both ends are covered, sufficient permissions to the project to copy and permissions to create a new project.

Thanks.
--------------------------------------------------------------------------------
+1

I really need this one!
--------------------------------------------------------------------------------
Harwant Pannu wrote:
> In my version (0.8.4.stable.2777), only administrators can create new projects. If the latest version allows permission grant to non-Administrators for creating new projects then the request makes sense. I will suggest the following logic to allow project copy to an individual:
>
> *if (__user is allowed to create new a projects__) AND (__user is a manager or something equivalent for this project__) then user can copy this project*
>
> This will ensure that both ends are covered, sufficient permissions to the project to copy and permissions to create a new project.
>
> Thanks.

I think both permission could exist, create and copy.

In my case I have a role that can only create sub-projects, and he has this role on a "TOP Project", now I'm using some projects like templates, and I need a role that can only instantiate this template projects, if I give him a role on this template projects with the copy_project permission, he's able to create new projects just from copies.

Did I make myself clear ?
--------------------------------------------------------------------------------
+1
We are creating template projects, but it won't be useful if people can't copy them to create their own projects. As it is now they always have to ask an administrator to create a copy.

An additional permission for copying would be great.

Pedro
--------------------------------------------------------------------------------
I know this is an old ticket but there hasn't been any movement. Any chance of this?
--------------------------------------------------------------------------------
+1

Necessary for our teams!
--------------------------------------------------------------------------------
+1 necessary on our side
--------------------------------------------------------------------------------
+1

Is there any updates on this feature?
--------------------------------------------------------------------------------
+1 Any nice soul worked on this?
--------------------------------------------------------------------------------
+1
and duplicated by #13373 and #17961.
--------------------------------------------------------------------------------

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

--------------------------------------------------------------------------------
+1
Having to start every new project from scratch to me seems quite unagile...
--------------------------------------------------------------------------------
+1
it would be so helpful !!!
--------------------------------------------------------------------------------
+1
Thanks in advance!
--------------------------------------------------------------------------------
+1
Would really save us some time as it removes a bottleneck! Thanks in advance!
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------

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

--------------------------------------------------------------------------------
+1 It's a basic function
--------------------------------------------------------------------------------
I have attached the patch.
Users with copy_project permission can copy from projects/show.

---

Even if you do not have view_issues permission of the copy source project, you can copy issues from the source project if you have copy_project permission.
If you change the copied project to public at that time, you will be able to see issues that you would not have permission to see.
That is, the copy_project permission includes various permissions such as view_issues, view_messages, and view_wiki.

I think it is necessary to discuss whether there is a problem with the copy_project authority as the authority design policy.
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
I've attached a patch, similar to the one above, where the user is allowed to copy projects if he has add_project permission. If one is allowed to create projects he should also be able to copy projects. The current user is also added as default member to the copied project, just like when creating a project.
--------------------------------------------------------------------------------
Markus Gerhold wrote:
> If one is allowed to create projects he should also be able to copy projects. The current user is also added as default member to the copied project, just like when creating a project.

I think it would be a security issue if users who have "Create project" permission are allowed to copy a project. This is because the user who has copied a project can have more permissions if "Role given to a non-admin user who creates a project" (Administration > Settings > Projects) is set.

Depending on the settings, users who copy a project will be able to see information in the destination that they are not allowed to see in the source project.
--------------------------------------------------------------------------------
Updated the patch for the latest trunk (r20739).
--------------------------------------------------------------------------------
I found an issue in the patch.

When a user attempts to copy a parent project, a validation error "Subproject of is invalid" is shown if the user does not have "Copy project" permission for subprojects.

I think the "Copy" button for the project should not be shown if the user does not have "Copy project" permission for subprojects.

"Delete project" permission (#33945) behaves like that. If you don't have permission for subprojects, "Delete" button does not appear on the parent.

--------------------------------------------------------------------------------
Go MAEDA wrote:
> I found an issue in the patch.
>
> When a user attempts to copy a parent project, a validation error "Subproject of is invalid" is shown if the user does not have "Copy project" permission for subprojects.

Steps to reproduce:

1. Apply attachment:4687-v2.patch
2. Load fixtures by running @bin/rails db:fixtures:load@
3. Grant "Copy project" privilege to Developer role
4. Sign in with the user "dlopper" (password: "foo")
5. Try to copy the project "eCookbook". You will see "Subproject of is invalid" error

--------------------------------------------------------------------------------
Will there be a day when this kind of _basic feature_ is implemented? ;)

There are a lot of patches out there regarding this..
On every update we have to fiddle out which one works..

Thanks alot..
--------------------------------------------------------------------------------
Can anyone please adress this for V5.0 please?
--------------------------------------------------------------------------------
Go MAEDA wrote:
> Go MAEDA wrote:
> > I found an issue in the patch.
> >
> > When a user attempts to copy a parent project, a validation error "Subproject of is invalid" is shown if the user does not have "Copy project" permission for subprojects.
>
> Steps to reproduce:
>
> 1. Apply attachment:4687-v2.patch
> 2. Load fixtures by running @bin/rails db:fixtures:load@
> 3. Grant "Copy project" privilege to Developer role
> 4. Sign in with the user "dlopper" (password: "foo")
> 5. Try to copy the project "eCookbook". You will see "Subproject of is invalid" error

I have attach a patch that resolves this probrem.
The copy_project permission cannot be enabled unless one of the :add_project or :add_subprojects permissions is enabled.
!{width: 500px; border: 1px solid #ccc}permissions.png!

This patch is under development, so applying it to the production environment is risky.
--------------------------------------------------------------------------------
Fix a problem with the disabled attribute of checkboxes.
--------------------------------------------------------------------------------


related_issues

relates,New,25154,Allow non-administrator users to copy certain projects
duplicates,Closed,17961,permissions for copy project
duplicates,Closed,13373,copy a (sub-)project as "non-admin" user
duplicates,Closed,7118,Possibility to allow users to copy a project

Admin Redmine さんが7ヶ月前に更新

  • カテゴリProjects_11 にセット
  • 対象バージョンCandidate for next major release_32 にセット

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

いいね!0
いいね!0