---
title: "Release notes 8.0.9 and 7.5.13"
canonical: "https://support.appfire.com/space/JCPP/3659661336/Release%20notes%208.0.9%20and%207.5.13"
format: markdown
---
**Release date**: 9/14/2026

This release includes new features, enhancements, and bug fixes for Clone Plus for Jira, versions 8.0.9 and 7.5.13.

---

## New features and enhancements

### Hide Clone+ button on archived issues

Clone Plus adds a new configuration property, `allowArchivedIssues`, so administrators can hide clone operations when the source issue is archived.

**Default behavior**: If the property is not set, archived issues can be cloned (same as before this change).

**To block cloning from archived issues**: Set `allowArchivedIssues = false` for the operation you want to restrict.

The property follows the same prefix rules as other clone settings:

| **Operation** | **Property key** |
| --- | --- |
| Default Clone+ (same project) | `allowArchivedIssues` |
| Default Clone++ (cross-project) | `plus.allowArchivedIssues` |
| Custom Clone+ slot N (1–8) | `N.allowArchivedIssues` |
| Custom Clone++ slot N (1–8) | `N.plus.allowArchivedIssues` |

Only an explicit `false` (case-insensitive) disables the operation on archived issues. Values such as `true`, `True`, or `FALSE` keep cloning allowed. Unrecognized values (for example `falsss`) are treated as allowed. Non-archived issues are always eligible regardless of this setting.

---

## Bug fixes

The following issues are fixed in this release:

- **Child issue cloning with renamed Epics**: Resolved an issue where child issues failed to clone (encountering a null issue type exception) when cloning an Epic in instances where "Epic" was renamed via Jira's native terminology settings.
- **Checkbox field deselection retention**: Fixed a bug where unchecking a pre-selected checkbox field on the Clone Plus creation screen was ignored upon submission. Newly cloned issues now accurately reflect deselected options.

---