Please advise if there is a simple setup to allow JIRA to return all rows when querying custom field or if it is a bug

JIRA v6.1.5

Created custom field "Issue Lapsed", found when query using this custom field would return max 30 entries on the worklist. Checked there should be over 100 entries but why only 30 entries are shown, there is no next page button so it looks like only 30 entries were being retrieved. Please advise if there is a simple setup to allow JIRA to return all rows when querying custom field or if it is a bug ? Kindly please help.

Terence. 

 

2 answers

0 vote

Could you clarify some details please?

>Created custom field "Issue Lapsed",

What type of field is this?

>found when query using this custom field would return max 30 entries on the worklist.

What is the query you are running?

>Checked there should be over 100 entries

How do you know that?

Thanks, the new custom field "Issue Lapsed" is a checkbox.

I know there should be over 100 entries as I could query the result using JIRA DB with custom field ID. However, only 30 entries can be shown when retrieved online if search by the custom field.

Many thanks, Terence.

What is the query you are running?

image2017-2-8 10:12:39.png

What is the text of the query you are using?

select * from customfieldvalue where customfield = 11501; ( where customfield 11501 is the newly defined custom field "Issue Lapsed".

No, what is the text of the query you are running?

Not SQL (it's technically right, but rarely answers the actual question for a user because the database is not built for reporting).  We need to see the questions you are asking JIRA.

the text of the query ?

I used both the advanced query :-

image2017-2-9 11:3:54.png

and basic query :-

image2017-2-9 11:4:46.png

both queries return only 30 records.

Thanks,

Terence.

Right, your SQL is finding issues.  Your searches are finding issues over a year old.  That's the difference.

 

No, it is not as a silly question as what you thought. Only those over a year old would have the custom field Issue Lapsed populated. Both the background SQL and the frontend query should return the same no. of rows.

No, that's not true.  You are currently asking two different questions of your data.  Try asking the same question.

There are other things it could be, but until you are asking exactly the same question of your data sets, we can't look at those.

Please try the same search.

it is a waste of time.

I have to assume that you have understood that you need to ask the same question of JQL and SQL if you want to compare the results.  Hope that's helped you see what is happening.

0 vote

I suspect that you have not reindexed after the custom field was added. You can test this by running the query, then edit an issue that should be in the results, then rerun the query. If the number of issues returned increased, then a reindex is needed. Perhaps just for one project. There may also be a warning about this when you go into the Admin, Issues, Custom Fields page?

 

Suggest an answer

Log in or Join to answer
Community showcase
Emilee Spencer
Published Friday in Marketplace Apps

Marketplace Spotlight: DeepAffects

Hello Atlassian Community! My name is Emilee, and I’m a Product Marketing Manager for the Marketplace team. Starting with this post, I'm kicking off a monthly series of Spotlights to highlight Ma...

53 views 0 3
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot