Clone EPIC & Stories to New Epic and link New Stories via Automation

[Melissa Lato]

I have been trying to write a manual automation rule to clone an EPIC (or the selected issue) with all its sub tasks and then link them all as they were in the original EPIC:

I have tried many variations of this but all the Stories seem to stay linked to the original EPIC. I feel like I am so close that someone hopefully will be able to confirm the final steps for linking them up.

Thanks in advance.

[Randy · Accepted solution]

The Administer Projects permission in the permission scheme for the project controls the ability to change project names.  Restricting this will also prevent them from the ability to edit project role membership, project components, project versions and some project details ('Project Name', 'URL', 'Project Lead', 'Project Description').

https://confluence.atlassian.com/jira064/managing-project-permissions-720412504.html

Perhaps you can adjust your reports to not depend on project name?

[Matt Doar]

Perhaps use Project Categories?

[Leslie Barrett]

We are a highly regulated business which restricts a lot of processes and policies here. I believe that I can use Profields to manage fields at a project level. Thank you much for your replies - much appreciated!

[Dale Keller]

If you have the ScriptRunner add-on you can create a Fragment to hide the Project Details link within the project administrators section.  We were experiencing the same problem where users were changing the name of the project within our production instance which then wouldn't match our development or customer test instance.  I'm including the fragment code which I used to not hide it from a particular group.  Hope this helps.

In the Hide what field you'll select:  jira.webfragments.view.project.operations:edit_project

import com.atlassian.jira.ComponentManager;
import com.atlassian.jira.security.groups.GroupManager;
import com.atlassian.jira.component.ComponentAccessor;

def groupManager = ComponentAccessor.getGroupManager();
def currentUser = ComponentAccessor.getJiraAuthenticationContext().getLoggedInUser();

if ( groupManager.isUserInGroup(currentUser, "jira-support") ) {
return true;
}

return false;

[Joe Pitt]

If you're looking for a technical solution to what should be a policy issue you're doomed to keep chasing your tail so to speak. Give the first one 2 days off without pay and they will learn. 

[Leslie Barrett]

100% agree :)