Public forms are coming to Jira

[#1]

Hi Atlassian Community,

Public forms are coming to Jira Cloud! This is a highly requested feature and I am excited to share the details of this feature below.

Public forms will enable teams to extend their work intake to all of their stakeholders - to other teams within the same organisation that may not have access in Jira, to external agencies, vendors and customers.

Forms are available in both business and software projects, whether they’re team-managed or company-managed. They can be created and managed by users with project admin permissions. Today, access to a form can be set to Limited (only those with access to create an issue in the project) or Open (anyone who can log into the Jira site). Soon, there will be a third option: Public. Any user, including those without a Jira license, will be able to make a submission through a public form.

If IP allowlists have been set-up by an Organization admin to specify who can access content in Jira, these will apply to who can submit a response to a public form. A user attempting to access a public form from an IP that’s not on the allowlist won’t be able to view the form. Read more on IP allowlisting here.

Things to know about public forms

Creating a public form

When Public is selected from the access menu, a default reporter must be set for work items created from form submissions. To protect sensitive information, certain field types will be hidden on public forms, including assignee, people, team, project, parent, sprint, version and label fields. Attachments will also not be supported on public forms.

As part of this release, we will also be enabling a Deactivate option from the three dot (more) menu in the form builder so project admins can deactivate and re-activate forms as needed.

Submitting a public form

An unlicensed user will be required to enter their email address when submitting a public form. Public forms are protected by reCAPTCHA, and if the verification fails, the submitter will need to complete a manual reCAPTCHA challenge.

Once a form is submitted, the email of the submitter and a smart link to the form will appear as a comment on the work item created. Two labels will also appear - form and form-<unique-form-ID>. The work item created from a form submission can only be viewed and edited by those with a Jira license and the correct permissions. 

Controlling public form availability in Jira

Jira admins will be able to disable public forms (found under global settings > products). This will disable "Public" from the access dropdown in the form builder and deactivate any existing public forms within the site. There are separate settings for team managed and company managed projects.

The product setting for public forms is now available on all sites and our support documentation can be accessed here. We have also started rolling out public forms and these will become available to all customers over the coming weeks. I hope that everyone is excited as I am for this release! Please let me know in the comments below if you have any feedback, questions or would like to share what use cases public forms will open up for you!

Please note, we have no current plans to merge Jira forms with the forms capability available in Jira Service Management and the experience outlined above applies to Jira forms only.

[Bill Sheboy]

Hi @Loretta Brunette 

Thanks for this great info!  Quick question: will pubic forms be available for all license levels of Jira, including Free license?

Kind regards,
Bill

[Loretta Brunette]

Hi @Bill Sheboy - yes! public forms will be available for all license levels including free 

[Vishal Banshraj Gupta]

Hi @Loretta Brunette ,

Thank you for this amazing news! My organization has been waiting for this feature. In the future, will we be able to allow not all restricted fields, but the attachment field on Jira forms with public access?

Thanks & Regards,

Vishal

[Loretta Brunette]

Hi Vishal

That's great to hear! We have no firm plans at the moment to support attachments but it is something we do plan to explore, especially if we get feedback on this. Can you explain a bit about your use cases and why attachments are important?

thanks!!

[Stefan Draber]

Hi @Loretta Brunette 

thanks for the update, great news and will definitely open new use cases for us! 

Another use case for us would be, to make the form available for unlicensed internal (not public) users, e.g. employees that work only in Confluence or employees that are only JSM customers.

They should also be able to add attachments, e.g. to support their feedback or bug report with a screenshot or something. And while I see why attachments are closed for the public, our internal non-Jira users are considered more trustworthy than an anonymous persona from the internet.

So, this would be another access level, something inbetween Open and Public, I guess. Is this something you're already exploring or plan to explore?

PS: Bye bye Issue collector, as an admin I won't miss you 😁

[Jyoti Mane]

Hello @Loretta Brunette

We seek to provide access to forms exclusively for unlicensed internal users, rather than the general public.

We require a setup akin to the access provided to Jira Service Management (JSM) customers or portal-only access in JSM. Is it currently possible to achieve this configuration with Jira public forms?

Thanks,

Jyoti Mane

[Loretta Brunette]

Hi @Jyoti Mane and @Stefan Draber - glad to hear public forms will be of benefit. 

One way to achieve internal only access to public forms is to utilise IP allowlisting on your Jira site if you are on a premium license. Only those within the IP range set will be able to view and submit a public form. 

@Jyoti Mane - depends exactly what configuration you need from JSM. But for a complete service desk solution, with two way communications with an unlicensed user and customer accounts, JSM is the best solution. 

[Jyoti Mane]

Thank you @Loretta Brunette !

Our use case is quite similar to Stefan's. We are on the JIRA enterprise plan and want to make the form available for unlicensed internal users (not public)

Like, in JSM, users with JSM customer access can access the portal without consuming a license. Though, we can restrict those JSM customers  as the internal users (specified domains only). 

[James Rickards (Spark-Nel)]

Love it. This is a great feature.

[Stefan Draber]

Hi @Loretta Brunette 

thanks for your suggestion. Unfortunately IP allowlisting is not an option for us, as our people work remote and not necessarily via VPN, so we can't break down the IP ranges.

[Loretta Brunette]

Hi again @Stefan Draber and @Jyoti Mane - this is definitely something we are open to exploring. If each of you can spare 30 mins I would love to jump on a call so you can talk me through how you would like this to work. You can book time in with me here. 

[Michiel Schuijer]

@Stefan Draber, @Vishal Banshraj Gupta and @Jyoti Mane   

This would have been possible if Atlassian had decided to implement/leverage Advanced/ProForma Forms instead of this very limited feature from Jira Work Management that nobody seems to want.

[Loretta Brunette]

@Michiel Schuijer - I'm interested to understand more about this, what does Advanced Forms offer that would specifically improve public forms? 

[Maksim Beliaev]

@Loretta Brunette 

That is a great addition!

Jira Software had an undocumented feature to access forms directly via URL:
https://warthogs.atlassian.net/jira/software/c/projects/<YOUR JIRA PROJECT KEY>/settings/forms/form/2/edit

Would it be possible to expose those as well?

Or is there a plan to bring this functionality together, so that current forms offer more control?
For example:
- An input field should not exist in Jira but still be recorded in the PDF attachment
- Default values like description templates

[Loretta Brunette]

Hi @Maksim Beliaev - There are no current plans to bring JSM and Jira forms together I'm sorry. But thank your for the feedback on the specific features you would like to see. 

[Tony Landowski]

This is a great feature. I am creating a form and running into an issue with restricted fields. Is there a way to manage whether a field is considered restricted on a Public form?

[Loretta Brunette]

not currently @Tony Landowski . What are the restricted fields that are most important to include?

[Stefan Draber]

Hi @Loretta Brunette 

I'd love to jump on a call with you to discuss our needs. Unfortunately we don't even have a bit of overlapping working times in our respective time zones, so I couldn't find a slot for us. But if you have any specific questions I can also try to answer them in detail via email or something.

[Tony Landowski]

@Loretta Brunette, the only field that we really need right now is the Component field.  And there is nothing sensitive within this field for our project.  What would you suggest?

[Sandy Tang]

Hi @Loretta Brunette I was wondering is the forms feature available for us in Jira Product Discovery as well? Thanks

[Loretta Brunette]

@Stefan Draber - i'll add in some evening sessions for the week of 28 April, let me know if one of these would work as would love to chat more.

@Tony Landowski - unfortunately there is no workaround for this currently, but something we may explore based on feedback so I'll be sure to loop back

@Sandy Tang - unfortunately know but i will make sure the JPD product team see your question here. I do know some customers will use a Jira form for intake and then an automation to create an idea in JPD

[Michiel Schuijer]

Hi @Loretta Brunette,

To answer your question:

>  I'm interested to understand more about this, what does Advanced Forms offer that would specifically improve public forms? 

One of the things I think is missing, is the possibility to add markup sections in between fields, to further clarify certain sections of the form, what is expected in ways of input requirements. The plain text descriptions under each field are not sufficient for this.

Of course, the lay-out of this new form type is very simplified, so sections are not available either, which would also be good to have, to make the form look and feel more user-friendly, whether it be for fields or additional markup.

Restricting who can view this form once it's submitted is also missing, which would be good to have, to make sure only people who need to know about or work on the form, can access it. Perhaps automation and security levels can manage this, but that requires yet again more work for us.

Concerning the reporter of such forms: In my current company, but also in previous ones, the project lead is usually not someone engaged in direct actions on project requests, but more high-level things. Having the project lead set as the creator is not wishful, and we'd want to choose someone to set as the creator, like "Automation for Jira" user or some account we don't need to spend another license on.

These are just some of the things I'd want to see, but basically everything available in advanced forms is what I would want to have, so I will not easily be swayed to use this one ;) 

Cheers

[Olha Yevdokymova_SaaSJet]

Hey everyone 👋

Jumping in as someone from the development team behind the Smart Forms for Jira add-on — and also someone who works closely with teams trying to streamline their request intake and workflows.

Really excited to see public forms coming to Jira  — it's a big step forward and definitely something the community has been asking for. But like many of you, we've also noticed some gaps — things like no attachments, restricted fields, or needing to map every form field directly to a Jira field.

Our goal with Smart Forms has always been to support the kind of flexibility that real workflows need — things like:

• Public forms with attachments

• Create new issues or add form to issue for submissions

• Multiple forms inside a single issue (great for layered workflows: intake + approval + NPS)

• Updating existing issues via form submission

• Flexible form appearance and customization with form logic and form field validation

• And the ability to work across JSM, JWM, JPD, and Confluence

We’re super happy to see Atlassian investing more in native forms, and we’ll be watching closely as it evolves — it’s a great direction. Just wanted to share what we’ve built in case it’s helpful for teams that need a bit more flexibility right now.

Happy to answer any questions if you’re curious how it works in practice!

[Forrest Lin]

Hi @Loretta Brunette , would 2FA login rules also apply to public forms? For example, any user outside of our org cannot log into our Jira site, but would they be able to use still see the public form and submit tickets using their own email address?