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; } } }

How do I create automation exception rules for cloning issue types

Gary Pallas

I'm trying to work out how to refine the existing (built in) cloning function for a particular issue type to effectively restrict some fields from being populated to the newly cloned record.

Example - cloning a change request include all fields apart from planned start and end date.

I guess my main challenge here is trying to find the appropriate method of restricting the automation trigger to only apply when issue is created via 'clone' rather than manual creation of new issue. From here I can apply the logic but I can't seem to figure out how to define this particular trigger scenario.

Feels like it will be very obvious but any help would be appreciated.

Thank you

Accepted answers

All comments

Tomasz Kowalczyk

When you're doing cloning action try to set planned start and end to empty value

Tim Kopperud

Hi @Gary Pallas, welcome to Atlassian Community.

When you clone an issue it will allways create an issue link to the source issue, hence you shold be able to use an automation rule with a Created trigger, and then add a filter looking for the Clones link type.

This will not work using an Edited trigger since the link might have been removed by a user. But when the issue is created the link exists, and can be used as a filter for further processing in the automation rule.

Below the filter within you rule you can then set or remove values from all wanted fields.

TimK

Gary Pallas

Hi Tim

This sounds promising and exactly the sort of association I was looking for to 'hook into' as the trigger for any honing of clone rules - thanks Tim - I'll give this a go. Appreciate the insight

Gary Pallas

Thanks Tomasz - yes this is exactly my thought process for this field - it was the trigger for identifying new issues created by 'cloning' that I was most struggling with. Appreciate your help

Gary Pallas

Struggling a little. It would seem that the clones link type doesn't exist.

To check this further I've tried to use this as a basis in a filter (including 'issueLinkType = clones' into the query) and nothing returns despite there being cloned issues within the wider parameters.

Is this the correct linkage I am looking for?

Adolfo Casari

@Gary PallasTry using the Refetch action to make sure the link actually exists after the Issue Created event.

Luka Hummel - codefortynine

Hi @Gary Pallas

If you are having trouble achieving your goal with Jira Automations, you could try our app Deep Clone for Jira. Deep Clone allows you to clone issues and make changes to the data that is being cloned. You can use the Field Editor feature to edit field values or clear them.

2024-08-30 14-37.png

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management