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

Can automation update custom field that isn't on edit screen?

Eli Albert_8dvprf

Hi,

I have an automation rule that clones issue, and I want that during the cloning some custom field (paragraph) will be edited.

this field shouldn't be visible in the original issue and it should be empty. only in the cloned one some value should be added.

I tried to add it only to view screen, but the automation throws some errors. the strange thing is that when I tried similar thing, but on "Number" field type, it worked.

Edit: I don't want this field to be "hidden". the purpose is that it will be displayed only when it has a value in it, and only the automation will be able to edit it. so, just need to find a way for automation to edit fields that are not on edit screen.

Thanks in advance

Accepted answers

Jakub Koc

Hi Eli,

I think it should be possible without much issues, can you share your automation?
In the cloned issue, that paragraph field should always be the same, is it some smartvalue or what exactly do you have in mind?

Good thing would also be making sure that in case for both of the issue types, projects or wherever u are copying that issue fields are configured properly.

All comments

Jakub Koc

Hi Eli,

Good thing would also be making sure that in case for both of the issue types, projects or wherever u are copying that issue fields are configured properly.

Eli Albert_8dvprf

Hi Jakub,

here is my rule:

The field "suspected bug title" is the paragraph.

when I removed it from the edit screen, I got the error:

Once the field is added back to view screen, the rule works fine

Jakub Koc

Let me know it that works for u:

[Project you are cloning from]
Suspected Bug Title - needs to be on the screen, to make it unable to be view on issue you can just delete it from issue view

[Projects you are copying into]
Suspected Bug Title - make field visible in the issue view

I believe even though it's the same issue or request type it can differ between projects.

Julian Governale

Keep the fields on the edit screen so you can actually edit the fields, but then in your field configuration, mark the field as hidden

Eli Albert_8dvprf

The project I'm cloning from and the target one are not a "constant". it depends on the field value and they're both should have the same configuration and screen.

I want the field to be displayed only when it has a value on it and be not editable by users, only by automation.

Eli Albert_8dvprf

I don't want the field to be completely hidden. only when it's empty it shouldn't be displayed.

Also, only automation should be able to edit this field.

Welcome!

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

Quick Links

Find more posts tagged with

custom-field

cloud

clone

automation

view

screen