User not able to submit form using link embeded on confluence page

[Arti Patil]

hello All,

We have multiple projects, who have linked a form link to confluence page for creating issue in Jira software projects.

Recently many of projects are facing issue where users are not able to submit form. As a site admin i am able to submit form but not a normal users. Getting below error message

Error message "We couldn’t create your issue. You do not have permission to modify reporter in this project."

Does anyone else faced same issue?

[sanam malleswari]

Hi  @Arti Patil

It looks like the issue is related to the Modify Reporter permission in the project's permission scheme. As a site admin, you have access, but normal users do not.

To resolve this:

1. Go to Project settings > Permissions in Jira.

2. Ensure the appropriate user roles (like Users) have permission to Modify Reporter.

3. Test the form again after making the changes.

Let me know if this works!

[Olha Yevdokymova_SaaSJet]

Hi @Arti Patil !
Yes — that "You do not have permission to modify reporter" error usually comes from the form trying to set the Reporter field, which by default requires special permissions in the Jira project. Most standard users (even those who can create issues) don’t have rights to set or change the Reporter, which causes that failure on submission.

If you're open to using an alternative like Smart Forms for Jira, there’s a cleaner workaround that avoids this issue entirely:

✅ You can add a dropdown field pre-filled with the list of users (like Reporters or Assignees) from the selected project.
✅ That dropdown can then be mapped to the Reporter or Assignee Jira field — all without needing to grant “modify reporter” permissions to every user.

Here’s how it works:

• Embed your form on Confluence

• The form shows a dropdown with users (pulled dynamically from Jira)

• The user selects from the list

• The form submits using a default reporter behind the scenes

• The selected name gets mapped into the actual Reporter field of the created issue

This lets users “choose” the reporter while you avoid exposing permission-sensitive fields — a much cleaner and safer approach, especially at scale.