Hi everyone,
We're currently using Jira Forms within our organization to allow internal users to submit requests/issues. One big challenge we're facing is that after submitting a form, the reporter doesn't receive any confirmation or direct reference to the issue they just created.
This creates confusion, as many users would like to return to the issue they submitted — whether to track its progress, add more information, or follow up.
As a workaround, we've set up an automation rule that sends an email to the form submitter with a direct link to the created issue. While this works, it feels like an unnecessary workaround for something that should ideally be handled natively by Jira or Jira Forms.
Is there a way to allow the user who submitted the form to immediately see or access the issue after submission — without relying on automation?
For example:
Displaying the issue key or confirmation screen with a link?
Automatically redirecting to the issue after form submission (for authenticated users)?
Any best practices we're missing?
Thanks in advance for any tips or shared experiences!
Hi @Przemysław Ferkaluk , can you confirm that you are using forms from a Jira Software project, and not Jira Service Management? I ask because "Forms" can be a lightweight issue collector for a Jira Software project, or something you attach to a request type.
To answer your question most directly, JSM is the solution to allow users who raise requests to immediately see or access their request and to follow the progress or add more information.
Hi @Laura Campbell
Thanks for your reply!
Yes, you're correct — I'm referring specifically to internal submissions using Forms in a Jira Software project, not Jira Service Management.
As I mentioned in the original post, the main challenge is that after submitting a form-created work item, there's no clear or native way for the reporter to see or access the issue they've just created.
Since we're using this for internal use, it's important for users (who are authenticated Jira users) to be able to track, update, or follow up on their submissions. Right now, without the automation rule we've set up (which sends an email with the issue link), users often get confused because the issue seems to "disappear".
It feels like a basic usability gap, especially since these are licensed users creating work items directly into Jira Software.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Przemysław Ferkaluk What do you like about using the form for people to create work items in a project versus having them using the regular Create experience? If the people creating tasks through the form have access to the projects to later track the progress, add comments, etc, they clearly have permissions on the project, and they could create the issue directly using the Create button. You can even customize that experience if you don't like what is included automatically.
I'll just put this here that JSM is probably ideal for what you're looking for... but if you really want to stay with Forms in Jira Software projects, you will undoubtably need to use workarounds like Automation notifying them by email, or adding them as a watcher, or creating a public filter for work items where the reporter is the current user and then training users to find all the tasks they've created with that filter. There do not appear to be any customization options for Forms right now other than the fields you include in it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.