When a required-field validator is enabled in our JPD workflow, cloning an idea does not complete correctly. The cloned idea is created, but some field values from the original idea are missing.
Removing the required-field validator restores normal cloning, including copying the affected field values. We have observed this when placing required-field validators on different workflow transitions.
We do not reproduce the same behavior in our tested Jira Software workflows.
Previously observed error:
Idea cloning complete with errors: An error occurred while cloning idea
Please investigate whether this is a JPD cloning defect or a compatibility limitation involving workflow validators.
Preconditions
- A JPD project with idea cloning available.
- An existing idea with the field being validated populated.
- Identifiable values in other fields, allowing comparison between the source and clone.
- A required-field validator configured on the affected workflow transition.
Steps to reproduce
- Open the source idea and record its status and field values.
- Confirm that the field targeted by the validator contains a valid value.
- With the required-field validator enabled, use the native Clone action.
- Record any error message and open the resulting cloned idea.
- Compare the source and clone, identifying fields whose values were not copied.
- Remove the required-field validator and save/publish the workflow changes as applicable.
- Clone the same source idea, using the same user and cloning options.
- Compare the results. In our testing, cloning works normally after removing the validator.
- Re-enable the validator and repeat to confirm reproducibility.
Transition-isolation detail to provide:
[Specify whether the issue also reproduces with no validator on Create and only one validator on a later transition. This has not yet been established in this report.]
Actual behavior
- With the validator enabled, cloning produces an error and/or an incompletely populated idea.
- Values can be missing even though they exist on the source idea.
- Removing the validator allows normal cloning.
Expected behavior
- Cloning should copy all field values supported by native JPD cloning.
- Required-field validators should evaluate the appropriate values when their associated transition executes.
- A validator on an unrelated transition should not interfere with cloning.
- If validation legitimately prevents cloning, the operation should provide an actionable error identifying the field and transition, rather than appearing successful while leaving an incomplete clone.
Questions for Atlassian Support
- Is this a known JPD defect? If so, please provide the public issue reference.
- Which operation or transition invokes the validator during the failed clone?
- Does native JPD cloning support required-field validators on Create and subsequent transitions?
- What supported workaround preserves both transition validation and native cloning?
