Pain in the neck to rename a custom field due to hard-coded JQL plain-text queries

Hi all,

Why are JQL queries hard coded with plain text for custom fields?  I just renamed a custom field and broke a bunch of saved filters in the process.  Why are JQL queries not set up to reference each field's specific ID number?

1 answer

1 accepted

1 vote

You can use names or ids to create the queries. It is up to the user to decide what they want to use.

People go for names to make the query more readable, and that is exactly the reason why that option is supported. Unfortunately, the filter will be broken if the field is renamed. No easy solution for that I am afraid!

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Posted Wednesday in Jira

Join our webinar: How 1B+ feature flag events helped us build the new Jira

Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...

145 views 0 4
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you