Cloning multi-level cascading select field

When cloning a issue, a different multi-level cascading select field option is added to the new issue.

I have a issue with a filled multi-level cascading select field (level1:a, level2:b).

Then I clone the issue and in the same field there is another option (level1:с, level2:d, level3:e)

Moreover, the options in the cloned task from a different field context should not be in this project at all.

The problem is observed only in one project and with one specific field

Why might this happen?

1 answer

0 votes

Hi @Kholboeva Ira welcome to the Atlassian Community!

Are you using the built-in Clone action by Jira or do you use a third-party app?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Hi @Dave Mathijs !
We use built-in Clone action by Jira

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

It's very strange that a Clone action would trigger this. Are there any automation rules configured with an issue created trigger?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

No, we have checked everything and no automations are configured exactly

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.