Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Automation for Jira Lite - label not applied

I've created an automation rule to have a new label added to every new issue created in a project SYS, without any extra rules.


The rule is never applied and there are also no logs that it's failing.

I've checked all the permissions, both me and the automation add-on are admins of SYS project and should have rights to edit any story.


Thanks in advance.


Screenshot 2020-02-05 at 09.56.19.png

3 answers

One step is missing there... you might need to indicate the issue created scope - in your case, the issue field condition should be narrowed down to Project. 

In the below example, choose your SYS project. It should work then.

Screenshot at Apr 28 19-33-10.png

0 votes
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Feb 22, 2021

Hi Anita,

It appears that for the Labels field you have choses Add new values option instead of Set value option. So, I am thinking that it wants to add a total new Label value that does not exist in your instance.

But in your case, the devops_new value probably already exists as a Label value. So click on the 3 dots menu to the side of the field and select Select value.

Then put in the value of devops_new there and save it. Publish it and then try a test issue. 

Found a solution to this? I'm having similar trouble.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events