Labels bug from 4th April 2025

[Veronika Kosová]

Hello,

from the beginning of April I have issue with custom field type = labels.

First automation add label to this field, and second automation has set delay (10 seconds), and after that creates subtasks. But from beginning of april there is a problem that if I put label to the custom field (manually or by automation), it doesn't write down the label to the field immediately, and I need to do some refresh issue website  to save the label. 

Example: field type labels is empty -> I put label "abc" .. and this label immediately disappears, and I need to refresh the page to see this added label visible in field.

But problem is that my automation is created as:

trigger when value changes for custom field type label (value added for all issue operations)

then wait 15s

then issue field condition: when value in custom field = ABC

then create subtask.

The trigger works, but problem is that (log): The following issues did not match the condition

But it is not true, because trigger is "value added" and the condition is "value = ABC". And both conditions have been met.:( It worked well untill the beginning of april.

[Bill Sheboy · Accepted solution]

Hi @Veronika Kosová -- Welcome to the Atlassian Community!

For a question like this, context is important for the community to help.  Please post the following:

• what type of project is this: company-managed, team-managed, JPD, etc.
• an image of your complete automation rule in a single image for continuity
• images of any relevant actions / conditions / branches
• an image of the audit log details showing the rule execution
• explain what is not working as expected and why you believe that to be the case

Until we see those...

I hypothesize the problem is in the condition type / syntax used.  Seeing all the details of your rule will help to validate that.

Kind regards,
Bill

[Veronika Kosová]

Hello @Bill Sheboy thank you for reply.

Project is company managed.

Issue: 

---

Automation:

Automation audit log:

And what's my problem:) The field "automation" was empty. I added value (screen 1), so the automation was trigered. But after 2 min waiting (I putted delay because I thought that may help), the automation result is that "the following issues did not match the condition". But it doesn't make any sense :( And this automation worked well several months (without any change), but from the beginning of April 2025 (4.4. it seems) I have this issue. The field is filled, but automation react like it is not filled. That's why I added the delay part, but it doesn't work anyway.

Thank you for help

[Bill Sheboy]

Thank you for that information, and...I just recreated the symptom you are seeing with a test rule for this scenario:

GIVEN a Jira project
AND a global / company-managed custom labels field is added to the project scope
AND there is an automation rule with a Field Value Changed trigger for that custom field
WHEN a label value is add to the issue's field
THEN the issue-updated event fires and can start the automation rule before the label data is available to the issue

Essentially, this is timing / racetrack error.  The exact same thing happens with the Issue Created trigger (although it is much worse in impact).  I hypothesize the extra processing for a labels-type field is causing this symptom; that is, the label is added to the all-possible labels list first and then it is added to the issue, resulting in latency.

The fix / mitigation is to add the Re-fetch Issue action immediately after that trigger (and then you may remove the Delay action).  This will slow the rule a bit AND reload the data before the rule proceeds.

Finally, I recommend working with your Jira Site Admin to submit this as a defect to Atlassian Support.  The reason is the Field Value Changed trigger is quite commonly used and people probably do not expect it to have this timing problem.

https://support.atlassian.com/contact/#/

[Veronika Kosová]

Hello @Bill Sheboy thank you very much for your help. 

Just for info:

I hypothesize the extra processing for a labels-type field is causing this symptom; that is, the label is added to the all-possible labels list first and then it is added to the issue, resulting in latency.

-> I don't think so, because I'm re-using the same label all the time (by default used by previous automation). So it's not about creating new labels.

I'll report the bug to Atlassian support.