Would like to weigh in on the use of attachments. Our organization requires the ability for non-Jira users to be able to submit social media publication requests to us and not having the ability to include an attachment is a serious hinderance that we've not encountered with other project management systems. Having this feature is critical to our work. We can manage our own risk regarding the attachment type etc.
Atlassian Team members are employees working across the company in a wide variety of roles.
May 14, 2025 edited
thanks for the feedback @Wil . I am currently looking at where we can fit this into our roadmap as this is an important feature for many customers. As soon as I have clarity on this, i will post here.
@Loretta Brunette - Are Comments available on the Public form between the submitter and whomever is working the ticket in Jira; similar to the way the portal is set up in Jira Service Management where the customer can communicate back and forth with an agent?
Atlassian Team members are employees working across the company in a wide variety of roles.
May 14, 2025 edited
Hi @Josh Dickerson - a submitter will need a Jira license and permission to view the issue in order to comment on the issue created. Back and forth comms with unlicensed users is only offered in JSM. Hope this helps even if its the answer you may not have been hoping for :)
In the samem vein as Mel, our organization requires the ability for non-Jira users to be able to comment on requests with us to have continutity of passed data. Not having the ability is a serious limitation. Please consider getting this into your roadmap that will be important to users globally.
We have been waiting for this feature since April when it was announced to be coming. We are on bundled release tracks and didn't get it in the May 13 release and I don't see it listed for June 10 release bundle. How will we know when it finally arrives? Within Admin settings we still see "Currently Rolling Out" but we have the toggles to Allow it in company & team managed projects. Yet, we still only see "Limited" and "Open" form permission settings.
Hi @Loretta Brunette This is a feature we have been wanting for a long time. It does not seem to be available in our environment yet. Assuming role out is still happening?
Atlassian Team members are employees working across the company in a wide variety of roles.
May 27, 2025 edited
@Josh Dickerson - no links don't expire - good question! As a Project Admin, you can deactivate/reactivate a form from the form directory or form builder however.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
public forms will not be coming to advanced forms in business and software projects. JSM will be the product which continues to enable this (i know this is not the answer you would like to hear but i hope this provides clarity)
I think I can speak for everyone who really, really appreciates Advanced Forms (formerly ProForma) in Jira Cloud) in suggesting that Atlassian try hard to make us non-JSM users happy. If that's you, please like this comment.
I see that Atlassian is actively improving native forms in Jira, and that's fine. But then go all-in! Keep enhancing native forms until they have feature parity with Advanced Forms. Then all the rest of us will have no reason to complain (other than the one-time overhead of recreating all our ProForma Forms as native forms).
Anyone know how to set default values (preferably hidden values) on these new service desk forms? I am trying to set the parent value of new tickets but I cannot figure out the automation to set the parent value (I am trying to set the key like to something like xyz-123). I can send notifications fine and I can make similar automations (or set default hidden values) in Jira but I just cannot figure out how to do this with the service desk.
Cool feature, but WHY would you auto-enable this?!?! Total security hazard.
This should be OPT IN by org admins, otherwise project managers who are more on top of the latest features might start creating these all over without admins knowing it's happening...
I've been playing around with automation to send an email confirmation of form submission, with a copy of what was submitted, but I have only been successful if the person has a jira user profile. If they don't (i.e a genuine member of the public) I have not been able to find a way to use automation to trigger an email.
great to see the announcement for the attachment update.
To clarify: With the latest update, non-logged-in Jira users can upload attachments in public Jira forms? Because before this was only possible when the Jira form was set to private (i.e., only for logged-in users). I described my problem months ago
Great feature—thanks for the work on this! I do have a question: when a public user submits a form and a ticket is created from it, how can we update or notify that user through the ticket?
Is notifying the public user a supported capability? I’ve been testing it but haven’t been able to trigger a notification to the public user so far.
Hi @Jane Barton sorry for the really late response, have been on leave.
Have you tried adding in your own custom text field e.g. 'Email Address' which the submitter of the form has to fill in. Then in your automation 'Send email' action, you refer to that field in the 'To' box e.g {{issue.customfield_xxxxx}} then when the Work (Issue) Type is created, it'll trigger using whatever is completed in that field. This only works though if the Submitter enters in a valid email address, otherwise Jira automation will say that it didn't work, because the email was invalid. A little out of hands, but if you make sure in the form prompt, that you tell the submitter to ensure the correct email address is entered, that should hopefully work.
68 comments