nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Issue created with multiple components can be cloned/separated and assigned to proper owner?

John Pettoruto

Hi all,

I'm trying to find the easiest and neatest way to clone a single ticket containing components into multiple issues.

Example: Access is needed to a single system and i have components set up to assign to the proper handler when its created. Easy. The tricky part is I'd like to avoid having the requestor submit a separate ticket for each system.

So ideally, we receive a ticket requesting access to systems A, B, and C. Again, I have set up components to assign to a designated /technician. I've been messing around with cloning, sub-tasks etc but it keeps coming out messy. Is it possible to have it so that we would have the parent issue, then using automation, it creates a separate issue via clone, subtask etc. for each system... A, B, C and they would individually be assigned to the designated technician?

Accepted answers

All comments

Fabian Lim

Hi @John Pettoruto

Why don't you share what you have so far and we can help you build it. Jira automation could do this for you.

I'm interested in the custom field you are using to determine the systems being used.

Thanks

John Pettoruto

Here is what i have so far. the "components" field are the systems that trigger each ticket to be broken out into separate subtasks/clones and assigned to the designated person. In this scenario, i'd have about 5 other automation rules for each component/system. I have not found a way to build all components into a single automation rule. Thanks for your response!

Bill Sheboy

Hi @John Pettoruto

You may do what you ask in one rule with the new advanced branching, which allows you to iterate over the values in a smart value/list. Please take a look at this article to learn how to update your rule to do this: https://community.atlassian.com/t5/Automation-articles/Branching-over-smart-values-in-Jira-Automation/ba-p/1741935

Best regards,
Bill

John Pettoruto

I've tried just about everything it seems. There doesnt seem to be a way to simply have a ticket/new issue created for each component that is set in the original issue. When there's a single component it works fine but when multiple components are entered, there doesn't seem to be a way to neatly break it down into multiple issues. It will copy all the components to the new issue, creates more tickets than needed, wont assign properly etc.

Bill Sheboy

Hi, John.

If you post your current rule perhaps I could offer ideas to help. I just tried what I suggested using the Advanced Branching and it worked to create separate issues for each component in the trigger issue. For example:

trigger: manual
advanced branch: with smart value of {{issue.components.name}} and a name you choose for the variable (e.g. varComponentName )
- action: create sub-task, using the branch variable as needed, {{varComponentName}}

John Pettoruto

Thanks for your help @Bill Sheboy

The below is now creating subtasks off of the components. But is it possible to have the component field itself copied/set in the sub task? I cant seem to get that field copied over from the original and subsequently set on the new sub task created. Ideally I would like the end result to look like screenshot2 but I had to manually set the components field and assignee

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud