Atlassian conceptsAtlassian Certified Jira Administrator for CloudJQL
ACP-120 advanced user features: what the exam tests
What ACP-120 asks about advanced user features: JQL, sharing and subscribing to filters, board limits, and what a move between space types loses.
A JQL query that uses OR will not show in basic search, yet the same query written with IN will. And a filter subscription emails only the first 200 results, however many the filter finds.
01 What does ACP-120 test about advanced user features?
A mock exam question about a saved search looks easy until it asks who may share it. Here the answer turns on JQL, filter sharing, subscriptions or what a bulk move keeps.
What the exam asks about in this domain
- JQL queriesClauses, keywords, and what basic search can show
- Sharing filtersWho can share, with whom, and public sharing
- SubscriptionsEmailing saved filters to users or groups
- Moving work itemsWhat a move between space types keeps
Know JQL, filter sharing, subscriptions and moves.
02 How is a JQL query put together?
A simple query, or clause, is a field, then an operator, then one or more values or functions. Keywords such as AND join clauses.
Advanced search also allows ORDER BY, which basic search cannot define.
A clause is a field, an operator and values or functions; IN translates to basic search where OR does not.
03 Who can share and subscribe to a filter?
You can share filters you created with groups, spaces, space roles or everyone, but only with groups or roles you belong to. If you cannot see the sharing settings, you need the Create Shared Object global permission.
Public sharing needs a Jira admin to allow it for the site, and Free sites cannot be opened to the public.
To email a filter to a group, you must belong to that group and hold the Manage group filter subscriptions global permission.
Sharing follows your own memberships; group subscriptions need their own global permission.
04 What do boards and moves leave out?
A filter has no limit on work items, but a company-managed board, backlog and timeline each show up to 5,000 at a time.
Bulk moving work items to a team-managed space is where data goes missing.
Moving work items from company-managed to team-managed
Lost in the move
- Component values
- Version and release data
- Story points estimates
- Velocity and Burnup history
Kept
- Most global custom field values
- Links to old keys, redirected
Component and version data never comes back after a move.
Summary
- A subscription emails only the first 200 results of a filter.
- Company-managed boards, backlogs and timelines show up to 5,000 work items at a time.
- Moving to a team-managed space loses component and version data for good.
Sources
- What is advanced search in Jira Cloud? | Jira Cloud | Atlassian Support
- Manage filters | Jira Cloud | Atlassian Support
- Migrate between team-managed and company-managed spaces | Jira Cloud | Atlassian Support
- Allow dashboards and filters in your site to be shared publicly | Atlassian Support
- What are global permissions, and what do they control? | Atlassian Support
- Work item limits in company-managed spaces | Jira Cloud | Atlassian Support