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

How to filter in custom field "Issue key" from other symbols that are not Issues


I have custom field for linking issues. I made automation rule that proof tat this field is not empty and link issue with pointed in custom field.

But sometames users fill uncorrect this field and automation rule stopped and showing error. How can I filter uncorrect "issue key" to make rule work smooth?


1 answer

1 accepted

1 vote
Answer accepted

You would need to find or write a listener that can check what people put in the field and correct or clear it.

However, why?  Why are you doing this with a custom field?  Why can't you simply ask your people to use issue links?  They won't let people enter invalid issues and have a search function to help them find the right one, and have a better view when the issues are viewed/

Thanks for advise, but this is not the answer for question

The first paragraph is.

The second paragraph is a better answer though - is there a reason you don't want to use the issue link field for what it is for?

Yes, the first paragraph is, but this is design of solution. And there is no answer, can I or cant't use Jira automation servises or may be JQL request and operators to realize that solution

Your "design" is a bad one, I'd suggest fixing that instead of botching something with code.

Automation can't help you with this, you'll need to write code that can validate the field and either tell the user they've entered junk, or take a guess at what should be entered.  

If you used issue links as intended, you wouldn't have this problem - it's got a search, it validates automatically, and won't go wrong if an issue is moved

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events