Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,551,972
Community Members
 
Community Events
184
Community Groups

Dinamic JQL Filter + pass arguments

Edited

Hello,

I would like to know if it is possible to pass some arguments to a JIRA SQL filter:

e.q.:

https://jira.zzz.com/issues/?filter=123456#

project in ( proj) AND issuetype = Bug AND created >= args[1] AND ORDER BY "args[2]" ASC

 

call: https://jira.zzz.com/rest/api/latest/search?jql=filter=123456&args=123,234&fields=assignee...

 

I really do not want to create a filter for each combination of parameters.

E.Q: filter by date - 2019-2020 results in a filter. 2020-2021 results in another filter.

It seems JIRA is very limited and cuts the result list - will NOT show more than ... a couple of hundreds of items, so a large number of filters must be (statically) created to get all results.

 

Thank you,

 

 

1 answer

1 vote
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Feb 08, 2021

Not in the UI.  You can build urls  like the ones you are suggesting outside Jira, but there's no variable substitution inside it.

Jira stops listing issues at 1,000 to prevent performance issues (but that's just the listing, the data is all in the results)

Could you explain what you are trying to achieve here?  We can probably give you a better technical solution than constructing urls by hand.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events