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

This widget could not be displayed.

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
Community showcase
Published Friday in Jira

New 5k User Limit and Other Cloud Updates

Hi all! Lauren here from the Enterprise Cloud marketing team.  I have some exciting Cloud updates from #AtlassianSummit that I wanted to share. We want everyone in your organization to be ab...

85 views 0 2
Read article

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