Cloning sub-tasks using jira automation

[Mary Mark]

Hello Atlassian Community. 

Looking for some help to clone sub-tasks tickets from the parent ticket and then update a field values based on condition.

I am checking if the cloned ticked for a 2 level cascade field called category/sub-category contains the following values: Contracting Third Party - Change / NA to MGA transfer

If the new cloned sub-task ticket contains those values then update/edit field values:

{
"fields": {
"customfield_10182" : { "value": "Remun - Block of Business Transfers", "child": { "value" : "NA to MGA transfer"} }
}
}

However, this also updates and edits the category/sub-category of the original sub-task ticket but I only want it to apply to the new cloned sub-task ticket without changing original value of the sub-task ticket

For example:

original sub-task ticket contains values: Contracting Third Party - Change / NA to MGA transfer

New cloned sub-task ticket contains values: Contracting Third Party - Change / NA to MGA transfer (Rule checks to see if this is true, then update values to: Remun - Block of Business Transfers / NA to MGA transfer)

but do not update the original sub-task ticket.

This is my automation rule:

Thank you.

M

[Alexey Matveev]

Hello,

You can go to project settings -> permissions.  If this permission scheme is used by other projects, copy the current permission scheme and associate the copied scheme to the project. Then revoke all users, role and groups from permissions.

[Thomas B]

Hi Luis -

I just created a permission scheme (JIRA ADMINISTRATION > Issues > Permission schemes) and you revoke all permissions for everyone in the entire scheme. Next, you go to your project (Projects > "ProjectName" > Project settings > Permissions > Actions) and assign whatever project you want to archive with that permission scheme. This will effectively keep the project in JIRA but hide it from all users including admins.

If you ever need to revive the project, just change the permission scheme. Hope this is helpful!

Thanks

[Joe Pitt]

I don't know if there is another option in the cloud. The simplest way is to apply a permission scheme that doesn't give any user access. The JIRA admin will still see it on their list and can change the permission scheme if needed. Here is an article about JIRA server. 

https://confluence.atlassian.com/jirakb/archiving-a-project-in-jira-server-950287459.html