Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Most efficient way to search for more than one JIRA ticket at once?

I would like to know the most efficient way to search for a batch of JIRA tickets at once, that are outside of the filter tools. For example; 1,000 JIRA tickets in one project, all with the same status; If I want to search for 50 specific tickets to export out of the 1,000, what is the quickest and most reliable way of doing this?

2 answers

The Advanced Search using JQL is what you need. But, it really depends on what differentiates the 50 tickets.

At the simplest level if you have the key for all 50 tickets you can use JQL to just get them that way. For example if it were three tickets you would do

key in (pro-01,pro-02,pro-03)

So, in your case you would do this putting all 50 ticket keys in between the parentheses.

Otherwise, you would need to figure out something else that differentiates those 50 tickets.

Hi @Georgina Wood 

You could filter them out based on their creation date or resolved date.

I'm not sure if the count will be be exact 50 but we can provide the date range and verify the count.

For Eg:

project = XXX and created >= "2019-06-01" AND created <= "2019-06-31"

Btw, you can use time as well in the query something like:

project = XXX and created >= "2019-06-01" AND created <= "2019-06-31 11:00"


There are few other fields which can also be used to segregate issues like

  • Reporter
  • Assignee
  • Priority
  • Component




Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

305 views 9 7
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you