Filters, personal settings & sessions

Saved filters store a search query (in JQL, Jira's query language) so you can reuse it without retyping it. This page covers creating and sharing filters, issue type schemes (which issue types a project can use), your own account details, and your login sessions. Dashboards are a separate topic — see the Projects page for those.

Example prompts

"Save this search as a filter called 'My open bugs'."
"Share the 'Sprint Backlog' filter with the whole Engineering project."
"List my favorite filters."
"What columns does the 'Overdue Tasks' filter show?"
"Set the columns on filter 12345 to summary, status, and assignee."
"Delete the old 'Q1 Report' filter."
"What's my default share scope for new filters?"
"Create an issue type scheme called 'Support Requests' with Bug and Task."
"Which projects use the 'Standard' issue type scheme?"
"Add the SUPPORT project to the 'Helpdesk' issue type scheme."
"What's my Jira username and email address?"
"What permissions do I have on this instance?"
"Update my display name to Jane Smith."
"Log me out of my current session."
"Invalidate my elevated WebSudo session."

What's available

Saved filters

Tool	What it does
`create_filter`	Create a new saved search filter from a JQL query.
`get_filter`	Get a single saved filter by ID.
`update_filter`	Update a filter's name, JQL, or description.
`delete_filter`	Permanently delete a saved filter. Requires confirmation.
`list_favourite_filters`	List your favorite (starred) saved filters.

Tool	What it does
`add_filter_permission`	Share a filter with a project, group, or everyone. Requires confirmation.
`get_filter_permissions`	Get all share permissions set on a filter.
`get_filter_permission`	Get a single share permission on a filter by ID.
`delete_filter_permission`	Remove one share permission from a filter. Requires confirmation.

Filter columns

Tool	What it does
`get_filter_columns`	Get the default display columns configured for a filter.
`set_filter_columns`	Set a filter's default display columns (e.g. summary, status, assignee).
`reset_filter_columns`	Reset a filter's saved columns to each viewer's own defaults. Requires confirmation.

Tool	What it does
`get_default_share_scope`	Get your own default share scope for newly created filters — a per-user preference, not an instance setting.
`set_default_share_scope`	Set your own default share scope for newly created filters. It changes your default only; nobody else's new filters are affected.

Issue type schemes

An issue type scheme controls which issue types (Bug, Task, Story, etc.) are available in a project.

Tool	What it does
`list_issue_type_schemes` `[ADMIN]`	List all issue type schemes visible to you.
`get_issue_type_scheme` `[ADMIN]`	Get a scheme's full details, including its issue types and default issue type.
`create_issue_type_scheme`	Create an issue type scheme from a name and a set of issue types.
`update_issue_type_scheme`	Update a scheme's name, description, default issue type, or member issue types.
`delete_issue_type_scheme` `[ADMIN]`	Permanently delete an issue type scheme. Requires confirmation.
`get_issue_type_scheme_associations` `[ADMIN]`	Get all projects associated with an issue type scheme.
`add_issue_type_scheme_associations`	Associate additional projects with a scheme, keeping existing associations.
`set_issue_type_scheme_associations`	Replace the full set of projects associated with a scheme.
`remove_issue_type_scheme_association` `[ADMIN]`	Remove a single project's association with a scheme. Requires confirmation.
`remove_issue_type_scheme_associations` `[ADMIN]`	Remove all project associations for a scheme. Requires confirmation.

Your account

Tool	What it does
`get_myself`	Get the currently authenticated user — your own Jira identity.
`get_my_permissions`	Get your own permissions, instance-wide.
`list_permissions` `[ADMIN]`	List all permissions definable on this Jira instance (not user-specific).
`update_myself`	Update your display name or email address. Requires your current password.
`update_myself_password`	Change your own password. Requires your current password.

Sessions

Tool	What it does
`get_current_session`	Get information about your currently authenticated session.
`create_session`	Log in with a username and password to start a cookie-based session.
`delete_current_session`	Log out of the current session. Requires confirmation.
`invalidate_websudo`	Invalidate your elevated re-authentication (WebSudo) session. Requires confirmation.

Things to know

Nine tools require an explicit confirmation step. Deleting or resetting (8): delete_filter, delete_filter_permission, delete_issue_type_scheme, remove_issue_type_scheme_association, remove_issue_type_scheme_associations, reset_filter_columns, delete_current_session, and invalidate_websudo — none of them can be undone. Sharing (1): add_filter_permission is new to this list, and is gated because sharing a filter with a project, a group or everyone widens who can see that saved search and its results — the same reason delete_filter_permission was already gated for the other direction. The agent should check with you before any of these run.
7 of the 33 tools on this page need JIRA_ADMIN_TOKEN, each marked [ADMIN] in the tables above; without it they are not advertised to the agent at all. They are the issue-type-scheme tools list_issue_type_schemes, get_issue_type_scheme, get_issue_type_scheme_associations, delete_issue_type_scheme, remove_issue_type_scheme_association and remove_issue_type_scheme_associations, plus list_permissions (the instance-wide catalogue of definable permissions — your own permissions, via get_my_permissions, need no admin token). Nothing about your own filters, columns, session or account is admin-gated.
Global sharing can be turned off instance-wide. If you ask to share a filter with everyone and global sharing is disabled on this Jira instance, Jira rejects the request.
A filter without custom columns falls back to your defaults. Asking for a filter's columns returns "not found" if no custom columns were saved for it — that just means it uses each viewer's own default columns instead.
Changing your password isn't the same as your login to Alces. update_myself and update_myself_password ask for your current Jira account password, which is separate from the token Alces uses to authenticate on your behalf.
Logging in is separate from how Alces authenticates. create_session performs the classic Jira username/password login and starts a cookie session — it doesn't affect or replace the token Alces itself uses. Likewise, delete_current_session logs out that session without invalidating Alces's own access.
The default share scope is yours, not the instance's. get_default_share_scope and set_default_share_scope read and write your own default — what your new filters and dashboards are shared with when you don't say. Setting it changes nothing for anyone else, and it is not an admin control. (It does cover dashboards as well as filters, even though dashboards are managed elsewhere — see the Projects page.)

See docs/api-catalog.md for the complete technical reference (every field, every parameter). For errors, see Troubleshooting.