Cannot clone issue: "No value present"

[Brian Sweet]

A user who has always been able to clone issues has recently been receiving the above error. Permissions haven't changed at all. They can still create and edit issues from scratch, so I don't know how else to address this.

[Andy Heinzer]

Hi @Brian Sweet 

Sorry to hear about this error.  I came across another case that appears to have the same error.  I created a support case on your behalf in https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-1089467

Please follow-up in that support case so that our team can investigate this further.

Thanks

Andy

[Brian Sweet]

Thanks!

[Christian Joel]

@Brian Sweet Any news from Atlassian so far? When I open https://support.atlassian.com/requests/JST-1089467/ there is only the message "Unable to display request". Does that mean, I don't have access?

I am running into the same problem, but on my site these is only one user affected in one specific project. Same thing, no changes at all in the last 3 month to users/fields/workflows, etc. The user has create issues permission and all of the sudden this single user is not able to clone issues anymore (create issues is working).

Furthermore, it would be helpful if the error message would inform you of WHICH field the value is missing...

EDIT:
I've tested a bit and can add that users with said issue when cloning only get the field summary and checkboxes for links and comments in the clone popup, while other users with the same permissions but no cloning error still have the assignee field.

EDIT2:
I found out that the only difference between the two users was that one of them had the Assign Issue permission. Giving this permission to the other user solved the problem! So you need to make sure that any user who shall be able to clone issues in a given project has the Assign Issue permission (no idea why this dependency exists).

[Trudy Claspill]

Hello @Brian Sweet 

Is it only the one user that has the problem? 

Is the problem with only one issue?

If it occurs for multiple issues, is it only issues in one project?

If it happens only for one user, have them try a different browser app, a private browser window (like Chrome Incognito), and clearing their browser cache.

Have you tried using the browser Developer Tools to look and the Networking and Console information that is available when this error occurs?

[Brian Sweet]

Is it only the one user that has the problem?

Happens with multiple non-admin users.

Is the problem with only one issue?

Happens with all issues.

If it occurs for multiple issues, is it only issues in one project?

We only have one project.

Have you tried using the browser Developer Tools to look and the Networking and Console information that is available when this error occurs?

Here's what I found when a clone is initiated:

{
"self": "https://versanthealth.atlassian.net/rest/api/3/task/208929",
"id": "208929",
"description": "Clone [redacted]",
"status": "FAILED",
"message": "Preparing cloning machine",
"result": "No value present",
"submittedBy": [redacted],
"progress": 0,
"elapsedRuntime": 0,
"submitted": 1736866275002,
"started": 1736866275118,
"finished": 1736866275370,
"lastUpdate": 1736866275370
} 

[Trudy Claspill]

I am flagging your post to raise it to the attention of Atlassian team members. You should hear from them within 2 business days.

[Robert DaSilva]

Hi @Brian Sweet , hope you're well!

• Are you attempting to clone an issue from one project to a second, different project?
• Are you attempting to clone into the same project as the source issue?

My initial thought is that if you're trying to clone into a different project, there may be an Field Configuration Scheme that has a custom field set to required, which is not present in the source project.

Alternatively, there may be a workflow post-function or validator on the target project that has a custom field set to required, and again this may not be present on the source issue.

[Brian Sweet]

It is being cloned to the same project as the source. I'm mainly confused as to what changed recently that caused this to happen: I'm the only admin and nothing has changed with the workflow, permissions, fields, etc.

It's also, seemingly, an error that has little-to-no documentation.