Loading...

XML

Word

Printable

Details

Type: Suggestion
Resolution: Unresolved
Fix Version/s: 3.7
Component/s: None
Labels:
- affects-cloud
- affects-server
Environment:

Hide
System Date Friday, 11 Nov 2005
System Time 10:59:09
Java Version 1.5.0_04
Java Vendor Sun Microsystems Inc.
JVM Version 1.0
JVM Vendor Sun Microsystems Inc.
JVM Implementation Version 1.5.0_04-b05
Java Runtime Java(TM) 2 Runtime Environment, Standard Edition
Java VM Java HotSpot(TM) Client VM
User Name SYSTEM
User Timezone America/Los_Angeles
User Locale English (United States)
System Encoding Cp1252
Operating System Windows 2000 5.0
OS Architecture x86
Application Server Container Apache Tomcat/5.5.9
Database type mssql
Database JNDI address java:comp/env/jdbc/JiraDS
Total Memory 127
Free Memory 105
Used Memory 22
Uptime 3 minutes, 42 seconds
Edition Enterprise
Version 3.4
Build Number 106
Standalone

Show
System Date Friday, 11 Nov 2005 System Time 10:59:09 Java Version 1.5.0_04 Java Vendor Sun Microsystems Inc. JVM Version 1.0 JVM Vendor Sun Microsystems Inc. JVM Implementation Version 1.5.0_04-b05 Java Runtime Java(TM) 2 Runtime Environment, Standard Edition Java VM Java HotSpot(TM) Client VM User Name SYSTEM User Timezone America/Los_Angeles User Locale English (United States) System Encoding Cp1252 Operating System Windows 2000 5.0 OS Architecture x86 Application Server Container Apache Tomcat/5.5.9 Database type mssql Database JNDI address java:comp/env/jdbc/JiraDS Total Memory 127 Free Memory 105 Used Memory 22 Uptime 3 minutes, 42 seconds Edition Enterprise Version 3.4 Build Number 106 Standalone

UIS:
102
Support reference count:
14
Feedback Policy:

We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

Description

NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

Problem Definition

Currently JIRA allows all users to clone issues (which can optionally be disabled entirely - see workaround). As a JIRA Administrator, I'd like to restrict the ability to Clone issues to certain groups only.

Workaround

(This will disable the Clone feature entirely)

Navigate to Administration » Add-ons » Manage Add-ons;
Select System (in the add-ons type box);
Filter by "issue operation";
Click on it, and select "XX Modules Enabled";
Disable the View Issue Ops Bar Clone Link module.

See KB: https://confluence.atlassian.com/jirakb/disable-clone-issue-in-jira-747836996.html

Original Description

The "Clone this issue" link doesn't mean anything to most of our users, so it would be nice to be able to remove this link. It should be another permission in the Permission Schemes screen (like the "Link Issues" permission)

Attachments

Issue Links

is duplicated by

JRASERVER-9375 need to disable issue copying

Closed

JRASERVER-10500 Could use a seperate permission for clone and create subtask

Closed

is related to

JRASERVER-14434 Removing Clone button from certain groups - add Clone Issue permission

Closed

relates to

JRACLOUD-8497 Ability to disable "Clone Issue" link per project

Future Consideration

mentioned in: Page Loading...; Page Loading...; Page Loading...

(2 mentioned in)

Activity

People

Assignee:: Unassigned

Reporter:: David Demner

Votes:: 267 Vote for this issue

Watchers:: 128 Start watching this issue

Dates

Created:: 11/Nov/2005 7:01 PM

Updated:: 18 hours ago