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

Automation : copy a custom field between EPICS of the same project

christophe demez_41euod

Hi,

Imagine I have a new project and I create my first EPIC, I have a custom field where I set a value. Example

uffective = "ABCD"

Later, once an EPIC is created, I wish to update all their field "uffective" to the same value than the first EPIC. This value must be the same for all the EPICS in the same project.

I'm trying to use automation for this, but I can't find a solution.

Here are the steps I have in mind:

1) Scheduled Query: all the EPICS with uffective is EMPTY
2) Copy value: copy the uffective value somewhere as a global variable (in the context of the automation)
3) Other query: for all the EPICS copy the value in the uffective field

Accepted answers

All comments

Callum Carlile _Automation Consultants_

Hi @christophe demez

If all Epics within the project need to have the same value given on creation, you could either set a default value for this field (so no need to use automation), or could you not just hard-code the value within an automation rule, if that rule is scoped only to that single project?

Or do you want the field across all other Epics to be updated if the field is updated on any of the existing Epics?

christophe demez_41euod

Thanks @Callum Carlile _Automation Consultants_ , but unfortunately I have plenty of project and the value is different for each project. I do not have any data/metadata on the project so I cannot copy from there. It is why I try to copy from any EPIC in the same project. You see ?

Callum Carlile _Automation Consultants_

Fair enough, this definitely sounds possible.

Could you just have a simple automation rule scoped to that single project which triggers on creation, has a condition to only action for Epics, then hard-code that value you wish to set for it within the Edit Issue action?

Or do you want it to be dynamic so that if the field value is changed on one of the Epics then it will change for all other Epics within the project?

christophe demez_41euod

It is an option, but in fact we have a lot of such projects, and adding more and more of them. It is why a dynamic approach will be better... the peoples that are managing such project doesn't have the JIRA automation skills.

Thibaut Subra _Elements_

Hello @christophe demez

I just checked your post and if you don't mind using third-party app, our Copy & Sync can give you a solution.

You can create what we call a recipe where you can define how you copy and synchronize fields, comments, attachments, or whatever.

So, in your case, you can create a recipe where, when triggered, you copy and synchronize the value of your custom field "uffective" from the Epic source.

That way, when you want to create a new Epic, you just open your source Epic, trigger the recipe and it will automatically create a new Epic with the custom field "uffective" with the value "ABCD". If you chose to synchronize this field as well (and not just copy it), when you will update the value of "uffective" on your source Epic, the field of all other Epics will be updated with the new value.

I hope this helps. If this is the case, you can try our app for free during 30 days (and it's lifetime free under 10 users).

Let me know if you have any questions!

Regards

christophe demez_41euod

Thanks, but we are not allowed to add any add-in into JIRA. I can't do that unfortunatly.

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server

atl-gruland

automation

smart-value