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

[Eli Albert]

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

[Jakub Koc · Accepted solution]

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.

[Eli Albert]

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.

[Eli Albert]

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.

[Jakub Koc]

What do you mean by that they're not constant?

Basically what i explained above, the configuration of both will be the same, the only change would be visual in the issue view, 

If you go to Project > Project Settings > Request Types > Service Requests > [Your chosen request type > Issue view, you can select field and mark it as hidden when empty. On the Issue it basically looks like this, moving field to "more fields" unless you put value in it, then it would automatically be moved to details

And Regarding locking field, I believe only option would be to remove that field from the edit screen, add a new transition that would be done by automation and make that field editable only there, check this documentation.

[Eli Albert]

I meant that sometimes I need to clone from project X to Y, sometimes from Y to Z etc., which means they have to be exactly the same.

"hidden when empty" still allows users to edit it when they expand the collapsed section

Anyway, it seems indeed that automation cannot edit unless the field is on edit screen.

Thanks Jakub!

[Jakub Koc]

Okay, so you are only left with option to make that field hidden when empty for all projects everything else would be just as I mentioned in the last message:)

I'm glad that we were able to solve this one out, do you have any more questions or will you mark it as resolved?

[Eli Albert]

It's kind of solved :) 
the original question was whether it's possible to make automation edit field without being on edit screen, but I can't find any answer to it even in Atlassian docs.

For now I can move it to hide when empty and it's good enough, not perfect though.

[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]

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.