Atlassian Team members are employees working across the company in a wide variety of roles.
December 3, 2024 edited
Hi everyone,
Thanks for the feedback on this post. We have taken on all the feedback on Advanced Forms aka ProForma, but for now we will continue to invest in the forms natively available in Jira, for a number of business reasons, various customer feedback sources and insights from our research. I know some of you do not agree with this approach and may be disappointed, but I want to be transparent here.
We have no current plans to remove Advanced Forms for those who have it enabled, nor to block the direct URL access.
Also, just to re-iterate, forms today are only accessible to those who have a Jira license, they cannot be opened up to the public.
I see the last comment is that this should be rolled out a couple of weeks ago. I don't see this available in our project yet. Can you confirm if this is available for on-prem?
@Sarah Palumbo No, this is not likely to be rolled out to self-managed/on prem or Jira Data Center, because it is mentioned at the top "Loretta here from Jira Cloud".
That is usually a good indicator something is released only on Jira Cloud and not for Data Center.
I wouldn't worry that you miss out, though, since it is not a very useful feature that is added and I don't know anyone who is going to use this.
I completely agree with @Michiel Schuijer and I’m confused about why you introduced Forms instead of using Advanced Forms, which have been available for some time. This functionality was not communicated either.
"When I saw the "Forms" menu in our Sandbox, I was excited at first. For years now, 'regular mortals' have asked for more simple input forms than presented via the "Create" button, and this seemed like the answer to me.
I quickly realised, however, that this menu has nothing to do with the (formerly Proforma) Forms that existed already for more than two years, the proper forms app that Atlassian bought from Stilsoft and has not integrated properly at all with Jira Software (JSW), ever since (2021?).
The Stilsoft Forms feature has been available under the hood for quite some time now, but instead of leveraging that and making those forms available from the side panel to all project users, we now get some weird forms menu that only showcases forms that can be shared in a convoluted way that defies all purpose, to me.
Then, why name it the same, if it is something else entirely than "Forms" that already existed before and is still accessible for JSW projects (https://<your-company>.atlassian.net/jira/software/c/projects/<KEY>/settings/forms)?
Why make this separate feature, when the separation between Jira Software and Jira Work Management is supposedly lifted, and there is just "Jira" now?
And (last) why push this feature without being able to hide this at global level. Yet another feature we can't hide from project admins, making it challenging to be a Jira Admin some more...
Sorry, but I just have a hard time following the strategy taken here. IF Atlassian really wants to compete with competitors in the field of tracking work items and managing these, getting people out of email completely to track work/tasks/issues/etc., then wouldn't it make sense to build in features that are currently available already, like out-of-office assistants, easy ways (forms!) to capture input with the click of a "Create" button of from the Forms menu (without needing to go full JSM which is aimed at and priced towards external customers) and such things?
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.
when I first commented on this article, I was quite happy to get a forms solution also for Software projects in Jira. At that point, I simply didn't know the "hidden" forms feature yet.
Now that I know it, I'm with all the others asking: why would you, Atlassian, keep your great (ProForma) feature hidden and populate a much worse other form feature instead?
For now, I have no reason to make any use of the official Forms feature as long as the hidden feature is so much better and available.
My largest hope (and disappointment) is that I was hoping that forms would allow me a method of capturing very project-specific attributes and storing the form as either an attached object, or formatted as a single field, e.g. a read-only text field.
Without this capability, I'm back to having to figure out if I allow additional custom fields for single-project requirements (something I work to avoid), and diminishing the value of forms. Why create another way to enter data?
@Michael Holianthat is exactly what Advanced Forms aka ProForma can be used for!
It is my go-to alternative to offer when people request a bunch of custom fields, just for a single (software) project. I also don't want to allow custom fields for such occurrences, because practice has shown me that is not worth the effort and maintenance. Often times, such projects are short lived or don't get off the ground, or worse, they need to be changed back to follow company standards, making all the work done already useless, and still more work is needed to revert it. The experience is painful for everyone.
Advanced Forms can solve this, to some extend, but the workaround available now for JSW, could use an update, so people can start a new form creation directly from the "Create" menu, or alternatively from the Forms menu in the sidebar.
Wishful thinking, I know, but I'm not letting this go quietly into the night.
Amazing! Is there any way to notify a product manager via email when a new form is submitted? Looked around under the notification settings but doesn't look like there's any way to enable notifications for Forms in particular.
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.
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.
We have no current plans to merge with the forms capability available in Jira Service Management and there will be no changes to any site which currently has these enabled for their Jira projects.
The acquisition of ProForma provided the opportunity for Atlassian to offer great functionality not just in JWM and JSM but also in Jira. But no. Feels like a sales and marketing play for more product licensing. Many Enterprise Cloud orgs have good reasons to not want or need JSM (or JWM), and they are left to suffer with the substantial feature gap with Forms in Jira Cloud.
I recommended ProForma as a forward-looking option, after Jira acquired them and well before a planned migration from Data Center to Cloud. Now I learn that ProForma features in Jira won't ever happen. Great. My full gripe in the Community Forum is here.
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.
I am sad to see "we will not be enabling this capability for business and software projects, as we aim to reduce customer confusion and streamline the form experience in Jira" because in my opinion the way to reduce customer confusion would be to implement ProForma/JSM forms in Jira so that everyone has the same experience and access to the best feature set. I suppose that might prevent some customers from spending the extra money on JSM however so this might be a finance-driven decision rather than a software design decision.
When submitting a form, the confirmation message only displays "We're on it! Thanks for your submission." However, it does not show the created ticket number or a direct link to the issue.
For internal use cases, is there a way to enable the visibility of the ticket number and link upon form submission, so users can track their requests more easily?
Atlassian Team members are employees working across the company in a wide variety of roles.
February 26, 2025 edited
Hi @Fred Quintero - it's not possible today but it is something the team are going to explore in the coming weeks. i will be posting another update on forms shortly too and will provide an update on this when I do
Hi @Loretta Brunette! Super excited for this new feature. I've started using forms, and working well so far. Will there be an option to link, or attach forms to issues, using Jira Automations? A use case would be that a reporter submits a ticket using forms, but the JS team needs to send another form to gather additional information. Similar to how it functions in JSM.
Another nice to have (similar to JSM forms) - if we could add fields without linking to custom fields. In my case, we have about 10 fields which we do not track for reporting, but still do need to gather the information. As a best practice, I would like to avoid using custom fields.
@Loretta Brunette Am I correct in that you could use a Jira Issue Collector on an external website to generate a work item from a non-licensed user? It would just have a more limited set of functionalities compared to forms...?
Atlassian Team members are employees working across the company in a wide variety of roles.
June 3, 2025 edited
that is correct @James Woyciesjes - the issue collector can still be used and there are a number of differences between this and forms. Also note that the issue collector only supports company managed and not team managed projects like forms do.
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.
@Fred Quintero: I came up with a solution for giving our users access to information about their submitted tickets. We create a Confluence page for that. We send users to that page to submit forms, where they find:
Confirmation about what form they can submit here (are they in the right place?)
A big button they can press to create a new form (URL just goes to the form)
A JQL macro listing all of their form submissions (JQL uses Reporter=currentUser() )
For that last bullet it helps if all form submissions have their own work item type. We use "Request" (instead of "Story" or "Task", etc) to keep them separate and easily identifiable in the backlog.
In addition, we have a separate workflow (and board) for Requests, which allows for triage, review, approval, design, analysis, additional details, and anything else needed before it's ready for the team.
Then we use an Automation rule as an action to change the Request to a Story, and update the Status to put it at the start of the team's main workflow. That last bit requires a common Status between the two workflows to enable the rule to change the type.
The net result is a Confluence page allowing users to submit forms, and to monitor all their submissions. Sorting the Jira macro to show most-recently-created-first ensures their latest Request shows at the top.
72 comments