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

continuous automation failure mail

백재현/DevOps

I recently created Automation at Global Scope. When an issue is created, if there is an approver field, write a comment referring to the approver.

The problem is, when an issue is created for a project without any Approver Field, SOME ERRORS occurs for some projects and NO ACTIVIONS PERFORMED for others.

Importantly, neither project has an Approvers field. In other words, I will be fine if both become NO ACTIONS PERFORMED, but I am puzzled that some projects have SOME ERRORS.

In the case of a project where SOME ERRORS occurs, the error message below is shown.

Could not find your configured field, it may have been deleted, or may need to be added to the project
Approvers

Whenever SOME ERRORS occurs, I receive a failure notification email. How can I change it to NO ACTIONS PERFORMED from SOME ERRORS?

Accepted answers

Trudy P Claspill

Hello @백재현/DevOps

Can you describe each step of your rule, or provide screen images (in English)?

Additionally can you provide the complete details of the rule execution Audit Log (in English)?

In order to give you advice we need to know which step is producing the error. We also need to understand the context in which that step is executing within the rule.

All comments

Trudy P Claspill

Hello @백재현/DevOps

Can you describe each step of your rule, or provide screen images (in English)?

Additionally can you provide the complete details of the rule execution Audit Log (in English)?

In order to give you advice we need to know which step is producing the error. We also need to understand the context in which that step is executing within the rule.

백재현/DevOps

Screenshot 2023-11-21 at 15.30.36.png

This is the rule detail

Screenshot 2023-11-21 at 15.31.29.png

This is the error case.

Screenshot 2023-11-21 at 15.32.18.png

This is the NO ACTION PERFORMED case.

Both LCC and TMAPBX doesn't have Approvers field

So I wonder why they have different error message.

Trudy P Claspill

Are both projects Company Managed projects? If so check if the field is present in the Field Configurations used by the issue types being created.

While both projects may not have the field on the screens, the one resulting in No Actions Performed may have the field in its Field Configuration. That would enable the rule to resolve the field reference. If the field is not in the Field Configuration for the project and issue where you get the error, that could be the reason for the error.

백재현/DevOps

Hi, the project that has an error is not the company managed project. this project is the team managed project. Will this be a problem?

When I see the Issue types of this project, it doesn't contain Approver field now, but it seemed like a situation that could add an approval field.

Wojciech Wardaszko_p20bth

@백재현/DevOps, @Saveliy Dzvonkevych

I'm with HeroCoders, the team behind Issue Checklist Pro, one of the apps affected by this error. We had some tickets about this issue coming from different customers.

It seems that Atlassian introduced something on the backend that affected fields with global contexts but no screens associated, like our Checklist Text field.

We do not yet know the inner workings, but adding any custom field to any screen in a project and removing it re-registers the field within that project's field configuration scheme. It is confirmed to work in team-managed projects as well.

You do not need to show the field in the issue view, just add it, save, remove it, save.

This should solve the issue.

Cheers,
Wojciech

Saveliy Dzvonkevych

@Wojciech Wardaszko @Trudy P Claspill

Thanks for your quick responses!

Honestly, I don't really understand how to make it work. Indeed, I use Checklist Pro, and everything used to work properly, besides, the steps you advice didn't help.

See the whole logic and attempts over there:

https://www.loom.com/share/4604548e3cd74bdeb7836db813af432a?from_recorder=1&focus_title=1

Is there any hope to resume the checklists in automation working?

Wojciech Wardaszko_p20bth

Hi @Saveliy Dzvonkevych

It became apparent yesterday that the solution I proposed was very short-lived - Jira database apparently clears the field association from the scope of automation rules soon after the field is removed from the last screen in any given project.

We have started to push back against this change, please see here: https://ecosystem.atlassian.net/browse/ECOHELPPUB-95 I'd appreciate it if you commented on this ticket saying this affects you if you have access to it.

In the meantime, one of our customers came up with a workaround - they created a placeholder issue type and added it in their projects, configured it with a separate screen configuration and added Checklist Text to that screen.

They never plan to use that issue type, but it registered the field within the project and restored their automated operations related to Checklists.

I hope this helps, as ugly as the workaround may be. We are determined to help our users with this. We are sorry that there was no heads-up, but this change surprised us greatly as it was not communicated with the developer community beforehand.

Cheers!

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud