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

Cloning from another project

Aaron McDonald

I have a personal task board that I use to help me prioritize my tasks and I'm attempting to setup an automation that will clone my tickets from another project that meet certain criteria. My query works fine in general search but when creating my automation, it doesn't find any issues. I noticed the "scope" of my automation is set to only my personal project but I'm not able to change it. Is this because the project is private? Is there any way that I can clone issues from other projects into my own while keeping it private?

Accepted answers

Marcus Jones

Hi @Aaron McDonald

Welcome to the Community!

Would be good to understand what you are using for your trigger and actions. Is it a scheduled trigger? If it is, and you're using a JQL query, you'll want to make sure the Checkbox next to "Only include issues that have changed since the last time this rule executed" is NOT checked. you can find it just under the JQL query box.

If it isn't that, tell us more about your automation so we can better help!

Joseph Chung Yin

@Aaron McDonald -

Based on your thread exchange with Marcus, you will need to obtain your site admins/jira admins support to change your automation scope to multiple projects instead of just for your personal project. This essentially makes your rule to a Global rule.

Keep in mind that once it is Global rule, you may loose your edit rights to the rule. In addition, you need to ensure the cloning a rule is an absolute necessity for your operations with the rule execution limits - See page - https://www.atlassian.com/blog/announcements/cloud-automation-packaging-update

You don't want to get into a situation where rules are created and executed causes your site to exceed the limitation. Once limitation is exceed, all rules executions will stop.

Hope this also helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

All comments

Marcus Jones

Hi @Aaron McDonald

Welcome to the Community!

If it isn't that, tell us more about your automation so we can better help!

Aaron McDonald

Hi @Marcus Jones

The trigger is meant to run on a schedule, once per day, to gather my tickets from a group project whose SLA is expiring that day, and clone the ticket into my personal board, into a "Due Today" status, with a due date set to today so that I know which tickets are needing an update.

The checkbox for "Only include issues that have changed since the last time this rule executed" is not checked.

In the "scope" section of the automation, its set to my personal project but it appears to be locked so I'm not able to add additional projects. Am I understanding correctly if the scope is set to my personal project, I cannot query and retrieve info from other projects?

Marcus Jones

Yes, that's correct. If the scope is set only to your one project, your JQL can be written to search for issues in other projects, but it will not return any results outside the scope. You can, however, change the scope in the global admin settings. Those settings are in System > Global Automation. Find your rule and in the rule details you can change the scope to Multiple Projects and then select the projects you would like to be included.

Aaron McDonald

I don't see where to edit the global automation settings. Could this be managed by my IT and hidden from me?

Joseph Chung Yin

@Aaron McDonald -

You don't want to get into a situation where rules are created and executed causes your site to exceed the limitation. Once limitation is exceed, all rules executions will stop.

Hope this also helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

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