Rule for clearing Component field has stopped working

Dan May 16, 2024
Hello,
We've started getting this error appear for all projects using a Rule setup for editing the Components field; clearing all Components.
Couldn't edit the Components field - the component doesnt exist
No fields or field values to edit for issues (could be due to some field values not existing in a given project)
Screenshot 2024-05-16 at 12.34.44 PM.png
Screenshot 2024-05-16 at 1.18.40 PM.png

This rule was working absolutely fine before using the following, but since yesterday morning it's now stopped working:

Screenshot 2024-05-16 at 12.52.51 PM.pngScreenshot 2024-05-16 at 1.17.07 PM.png

Screenshot 2024-05-16 at 12.46.05 PM.png
It's a rule to simply clear all Components when issue is transitioned to Done.
Any ideas to help what may have changed or gone wrong here?
P.S. We don't use Compass components.

Edit
I have a feeling this is what the field displayed when the rule was previously working completely fine a few days ago (screenshot found online):
Screenshot+2023-06-22+at+15.57.25.png
So wondering if a recent update to Automation has changed this at all?

3 answers

2 accepted

2 votes
Answer accepted
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 16, 2024

Hi @Dan -- Welcome to the Atlassian Community!

I just replicated that symptom, and this seems related to the recent Compass changes for components.  I recommend working with your Jira Site Admin to submit a defect here: https://support.atlassian.com/contact/#/

As a workaround, please remove the component field from the dropdown selection, and use advanced edit with JSON under "More options" to clear the field:

{
"fields": {
"components": []
}
}

Kind regards,
Bill

Dan May 16, 2024

Phew, this workaround works perfectly.

Thank you very much!

Like Bill Sheboy likes this
1 vote
Answer accepted
Paulus
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 22, 2024

Hi all, thanks for being part of the Atlassian Community.

We identified this to be a bug related to a recent rollout. We have now fixed the issue, so you should once again be able to clear all Components on an issue by leaving the field blank.

Cheers,

Paulus

Dan May 23, 2024

Hey Paulus,

Thanks a lot for the update!

While the Component field continues not to display 'This field will be cleared' when left blank, I can confirm the issue is now fixed and the Rule is working again.

Best,
Daniel

2 votes
Matt Parks
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 16, 2024

What do you see if you try to create a new component in the existing Automation rule to edit the 'Component/s' field?

I'm on DC (9.12.4) and I still see the 'This field will be cleared' message if I don't put in any specific Component(s) in my rule.

Dan May 16, 2024

Firstly, thank you for confirming it did used to display 'This field will be cleared' if left blank then.

And yeah unfortunately the exact same problem occurs when just trying to add it in again...

  • Just to show I included the Sprint field as example to show other fields are behaving correctly

Screenshot 2024-05-16 at 4.52.17 PM.png

So if this is an issue introduced live on Jira Cloud, really hope this get resolved asap as it's wreaking havoc on our automation rules :'(

Screenshot 2024-05-16 at 4.57.43 PM.png

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events