---
title: "3.2.20 Release notes"
canonical: "https://support.appfire.com/space/PSJC/3237937187/3.2.20%20Release%20notes"
format: markdown
---
> Macro (aura-html)


**Release date: **5/15/2026

This page outlines the updates included in the latest release of Power Scripts for Jira Cloud.

---

## Enhancements

The following enhancements are included in this release:

### Improved custom field options functions

The following functions now accept a context name or context ID as an alternative to the project and issue type mappings when identifying which context to target:

- [admGetCustomFieldOptions](https://appfire.atlassian.net/wiki/spaces/PSJC/pages/791511311)
- [admAddCustomFieldOptions](https://appfire.atlassian.net/wiki/spaces/PSJC/pages/791282009)
- [admUpdateCustomFieldOptions](https://appfire.atlassian.net/wiki/spaces/PSJC/pages/790528847)
- [admDeleteCustomFieldOptions](https://appfire.atlassian.net/wiki/spaces/PSJC/pages/790627240)

Previously, these functions required a `JProjectIssueTypes []` value to identify the context, which combines projects with arrays of issue types. This approach did not work for contexts scoped to a project but configured to apply to all issue types, since there was no way to represent "all issue types" in the required format. You can now achieve this by using an empty array of issue types.

> ℹ️ Example: a custom field context applies to a project with no issue type restriction. Previously, passing an empty array for issue types returned an error. Now this is fixed but you can also identify the context by name instead:
> ℹ️ 
> ℹ️ ```javascript
> ℹ️ admUpdateCustomFieldOptions("My Select Field", updatedOptions, "ACME Project Context");
> ℹ️ ```

Passing the context name is also more readable and resilient: if project keys or issue type configurations change, scripts that reference the context by name continue to work without modification.

---