ArtUp Query for Jira Cloud
JQL functions with complete answers
Subtasks and links of a query, sprint dates and history, comments, attachments, date and field math — in the ordinary Jira search, filters and boards. Write issue in subtasksOf("project = DEMO") and the result follows your edits. You get the full result or a clear error with the numbers, never a cut-off list. The app only reads your work items and runs on Atlassian.
- Runs on Atlassian
- Free for up to 10 users
- Works with in and not in
- 26 languages, light and dark
// Work items blocked by something that is not done yet
project = DEMO AND issue in linkedIssuesOf("project = DEMO AND statusCategory != Done", "is blocked by")
// What was added to the sprint after it started
issue in addedAfterSprintStart("DEMO board")
// Logged more than 20% over the estimate
issue in expression("project = DEMO", "timespent > originalestimate * 1.2")
Three things that set it apart
The complaints about the existing JQL add-ons are stale results, incomplete results and data kept by the vendor. ArtUp Query is built around the opposite.
-
Complete, or an error that explains
A result is never partial. On a test site with 50,000 issues every function matched a reference computed from the Jira REST API: 24 of 24, 85 of 85 (a sprint of 1,093 issues among them) and 17 of 17 checks.1 How many issues one function can read depends on the function and on Jira's API allowance for apps; a subquery that is too large gets an error that names the limit and how far to narrow it.
-
Kept up to date from Jira events
After an edit the result follows on its own. With room in the hour's allowance, a changed label or link showed in the result in about 15 seconds on a test site; with about 100 functions in use the 90th percentile was about 277 seconds. Bulk edits beyond the hour's allowance wait for the next half hour or hour, and a result too large for the allowance is an error with the numbers.
-
Runs on Atlassian, writes nothing
No external servers and no egress. The app reads work items and keeps only ids, dates, metadata and the arguments of the functions in use in Forge storage. It never edits an issue and does not ask for
write:jira-work.
27 functions in eight groups
All of them work with in and not in, accept any JQL, a saved filter or a list of keys as the argument, and nest. Full reference with examples in the documentation.
Work items of a query
subtasksOf,parentsOf,epicsOf,issuesInEpics,childIssuesOf,linkedIssuesOf,linkedIssuesOfRecursive,linkedIssuesOfRecursiveLimitedLinks and subtasks
hasLinks,hasLinkType,hasSubtasksBoard sprints
previousSprint,nextSprintSprint dates
sprintStartBetween,sprintEndBetween,sprintActiveOnSprint history
addedAfterSprintStart,removedAfterSprintStart,completeInSprint,incompleteInSprintComments
commented,lastComment,hasCommentsAttachments
fileAttached,hasAttachmentsCompare fields
dateCompare,expression
Change one word
Function names and arguments are the same where the meaning is the same. Write issue in instead of issueFunction in. ScriptRunner Enhanced Search on Cloud works only on its own search screen; ArtUp Query works in the standard Jira search, in filters and on boards. The differences are listed in the documentation.
// ScriptRunner
issueFunction in subtasksOf("project = DEMO")
// ArtUp Query
issue in subtasksOf("project = DEMO")
How it works
Three steps, no configuration.
- Install.
A Jira administrator installs ArtUp Query from the Atlassian Marketplace. Sites with up to 10 users use it free.
- Look up a function.
Open Apps → ArtUp Query: every function with its arguments and an example you can copy, and the state of the index.
- Search.
In the Jira search, switch to JQL and type
issue inand a function. Save it as a filter or use it on a board.
Honest about timing and errors
Edits reach the results through Jira's change events, which arrive in a queue. With room in the hour's allowance, a changed label or link showed in the result in about 15 seconds on a test site; with about 100 functions in use the 90th percentile was about 277 seconds; bulk imports and bulk edits beyond the hour's allowance wait for the next half hour or hour. A new site builds its index once, at the pace the allowance permits (about 840 work items per hour for the sprint history on a busy site, so a project of 10,000 work items takes about 12 hours), and until then the sprint, comment and attachment functions answer “Index is building: n of m issues”. A wrong argument, an unknown board or a result that is too large produces a message in the JQL editor that tells you what to fix, with the numbers, instead of an empty or cut-off list.
Your work items stay on Atlassian
ArtUp Query runs on Atlassian Forge. There are no ArtUp Labs servers in the path.
- Runs on AtlassianNo external servers and no egress.
- Never stores textThe index holds ids, dates, status categories, comment and attachment metadata and file extensions — not issue text, comment bodies or attachment content.
- Only reads your issuesNo
write:jira-work. The one write scope,write:app-data:jira, saves the results of JQL functions. - Exclude projectsAdministrators can keep a project out of the index and reindex it.
- No arguments in the logThe error log keeps the function name and the message, never the JQL you passed.
- Company- and team-managedWorks in both kinds of projects, on boards and in filters.
Guides
How to do it in Jira Cloud without an app first, then with ArtUp Query — with numbers measured on our test site.
- Subtasks of the issues in a filterWhy parent in (…) takes only keys, and subtasksOf
- Nested JQL queries and the 1,000 limitHow to check that a nested result is complete
- Added or removed after sprint startSprint history functions checked against the sprint report
- Linked issues of a filterlinkedIssuesOf, link types and recursion depth
Free for up to 10 users
Larger sites subscribe through the Atlassian Marketplace, billed by Atlassian with your other apps: $175 per month for 200 users. Start a free trial from Jira's Apps menu.