Community
Q&A
Jira
Questions
Pain in the neck to rename a custom field due to hard-coded JQL plain-text queries

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

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

1 vote

Answer accepted

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!

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Thanks

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Forums

Q&A

Community resources

Support

Top groups

Community resources

Support

Learn

Community resources

Support

Events

Community resources

Support

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

1 answer

1 accepted

Comments for this post are closed

Was this helpful?

Thanks!

TAGS

Community showcase

Atlassian Community Events