Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Cloned sub-task doesn't change it's account

tomas.kadlec
Contributor
March 22, 2022

Hi,

the question might sound dumb, but -

We have slight issue with tickets, sub-tickets and changing their accounts after being cloned.

Here's what we are doing and what the problem looks like:

We create ticket "T1" with account "A" and also create sub-task "S-T1". Account in sub-task is inherited.

When I change the account from "A" to "B" in "T1" ticket, account is correctly being updated in sub-ticket "S-T1".

If we clone ticket "T1" to "clonedT1", also with all of it's sub-tasks, account is correctly cloned too.

But when we change the account in ticket "clonedT1", account is not being updated in it's sub-tasks. Account there is same as during initial cloning.

Is there any other solution to this? Does it have any workaround?

 

Currently we are using JIRA server, but we'll be migrating to cloud soon

 

Thank you

1 answer

0 votes
Fabio Racobaldo _Herzum_
Community Champion
March 22, 2022

Hi @tomas.kadlec ,

you should put in place an automation so that, each time that account is changed on the parent all subtask will be updated.

My suggestion is to use https://marketplace.atlassian.com/apps/1215460/automation-for-jira-server?hosting=server&tab=overview

Hope this helps,

Fabio

Suggest an answer

Log in or Sign up to answer