Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How do you build your JQL filters ? And presentation of my Plugin

Deleted user
October 11, 2018

Bonjour à tous, Hello everyone,

 

When you build a JQL filter, do you use customfield's id or customfield's name ?

 

I prefer write JQL with the ids because when I change the customfield name, my filter still work.

But I lose my understanding, when I look my JQL... I don't know to what these id refer to...

 

So I made a little plugin who "translate" JQL like this :

 

Sans titre 1.jpg

How do you feel about this :) ?

 

1 answer

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
October 11, 2018

Filters are aimed at the human users, so I think most of us use the field names, as they're clear on what they are for (assuming you have a good admin who forces good choices of field name).  Your users do not want, or need, to have to understand custom field ids.

The plugin is nice for those who create filters for others in systems where field names do get changed a lot.

But if you're changing field names a lot, it begs the question of "why"?  I've looked after installations with thousands of custom fields and the only time field names should really be changed is when doing system stuff like "sorting out the mess of thousands of fields" or "merging systems", or "splitting and getting better names for stuff"

Deleted user
October 15, 2018

You totally right, the filters are for human.

 

At the start, this plugin translate mostly filter's id, because most of my filter are like :

filter = "abc" AND filter = "xyz"

But these filters name are changing too.

 

Why these name are changing ? Because our application is still in dev, so we aren't fixed...

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events