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

I cannot assign some labels to cards, because they are automatically removed

Carles Mata

I have a strange situation lately, where I assign some labels to Jira cards, and they automatically disappear from that card. For example, this one:

This `claude` label is new, so I could think that there's something with that label. But it also happens with a label that we have been using for the last 2-3 years.

We ran out of automations for this period, so it cannot be Jira Automation.

Automation rules for one or more of your products have stopped running because you've reached your monthly limit.

Anyone know where can I find out the reason? I don't see how can I debug this.

Thank you in advance!

Accepted answers

Gor Greyan

Hi @Carles Mata

Did you check other automation tools, like ScriptRunner(Listeners) or External Integrations (e.g., Exalate, API syncs, apps)?

These can overwrite the Labels field right after you edit it.

All comments

Gor Greyan

Hi @Carles Mata

Did you check other automation tools, like ScriptRunner(Listeners) or External Integrations (e.g., Exalate, API syncs, apps)?

These can overwrite the Labels field right after you edit it.

Arkadiusz Wroblewski

Hello @Carles Mata

Well @Gor Greyan It’s not just Automation Tools that can do that. Automation itself can also overwrite the current labels if it’s configured incorrectly. There are several possible causes.

Gor Greyan

Dear @Arkadiusz Wroblewski

I didn't say, that automation can't do that, but @Carles Mata mentioned that they ran out the automation limit, so the automation itself should not be the reason for this case.

Surely, wrong automation logic can be the reason for this case.

Arkadiusz Wroblewski

@Gor Greyan With this behavior, he could even hit the automation limit, especially if the rule actor is configured as that user.

@Carles Mata We need more input. Did you check the audit log? Since every instance is unique, it’s always like looking for a needle in a haystack.

Carles Mata

Hi Gor,

Thank you! You pointed me to the right direction. Looks like we have an external integration (a n8n instance) that was overriding the labels due to misconfiguration.

As labels were changing so fast (always with less than 2-3 seconds), I was just assuming that it was something internal on Jira.

We have modified the workflow, and now everything returned to normal state.

Thank you!

Carles Mata

Hi Arkadiusz,

As Gor said, it was not Jira's Automation, because I ran out of minutes last week. It happened just today, so this was the only thing I had for sure.

It finally was a n8n workflow that we had incorrectly configured. It was happening so fast, I didn't notice that it could be an external actor. But it's solved now.

Thank you anyway for time!

Gor Greyan

Dear @Carles Mata

Glad that could help you.

Have a good day

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud