[#JRA-14378] Ability to restrict 'Clone Issue' by PROJECT

JIRA

Ability to restrict 'Clone Issue' by PROJECT

Created: 31/Jan/08 03:13 PM Updated: 31/Jan/08 10:55 PM

Component/s:

Web interface

Affects Version/s:

3.10.2

Fix Version/s:

None

Time Tracking:

Not Specified

Participants:	Anton Mazkovoi [Atlassian] and Mary LeMieux-Ruibal
Since last comment:	24 weeks, 2 days ago
Labels:	restrict clone

Description

« Hide

The solution provided to ~~JRA-8497~~ will not work in our case.
This is related to the 'working as designed' described in ~~JRA-10210~~

We would like the clone ability to be shut off for only one project in our JIRA. This is because when an issue is cloned, it does not automatically get assigned to the default assignee and therefore there is not an e-mail sent via our notification scheme to the appropriate persons. We are encouraging users to re-open issues rather than clone them so they are not lost. However, this is not working so nicely. Is there a way to simply turn 'clone' off for a single project without affecting all projects within that instance of JIRA?

Thanks.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] - 31/Jan/08 10:53 PM

Mary,

It is not possible to restrict this per project. The only way is to edit the JIRA source and put some extra logic into the Clone Issue Operation that is used to display the link. This will involve editing JIRA's source and porting the change to every new version.

At the moment, we are not looking to add the ability to restrict the Clone Issue operation per project. The operation is protected by Create Issue permission.

Cheers,
Anton

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] - 31/Jan/08 10:55 PM

For more information on the way new feature and improvement requests will be scheduled please see:
http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+and+Improvements

Cheers,
Anton