I do not understand why this is different from JSM forms? The "forms" feature in JSW and JWM are completely useless as only the normal fields can be used. You acquired with ProForma a fully functional forms app and now you offer a completely useless feature as the newest thing in the world. Now we have to use a third party app to provide real forms functionality in JSW and JWM.
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 or from the Forms menu (without needing to go full JSM which is aimed at and priced towards external customers) and such things?
@Michiel Schuijer I know others probably have mentioned this but I didn't realize you get to "advanced forms" thanks for the url. I probably missed that in other comments.
I have to agree with your comments. Nice write up.
@Loretta Brunette I just realized that the proforma forms feature can be used in all projects by just adding /forms after the /settings in the URL of the project settings.
@Loretta Brunette will this, or the proforma feature accessible by adding /forms after a project's /settings url, be made available for Discovery projects? The current idea collection capability is extremely limited due to the lack of any form intake feature.
Atlassian Team members are employees working across the company in a wide variety of roles.
November 21, 2024 edited
@Christof Hurst - this was not by design. The recommended forms for Jira software and business projects are the ones natively available, we do not recommend the workaround of adding /forms to the URL to access ProForma and cannot guarantee that this will be available indefinitely
I know this may not be the answer you were hoping for but i hope that helps
Atlassian Team members are employees working across the company in a wide variety of roles.
November 21, 2024 edited
@Jone@Ashleigh Lodge - i have confirmed with the Jira Product Discovery team that intake and feedback, including forms, is next on their roadmap! they are in discovery at the moment
Although we might not use this feature due to lack of ability to raise a ticket without a license, I do see another issue here if JSW users wants to implement this, maybe there is a solution that I don't know.
e.g.
Every JSW user is used to hit the create button in order to create a ticket, how to prevent that one would do the same on a JSW open project since the project is now using forms?
e.g. If a user hits create, is there a way to take the user to the page that has the forms?
@Joao Zampa We want to use the proforma forms outside of JSM projects to provide specific data in the issue without creating to many customfields. Also dynamic forms will be possible. This all does not work with the JWM forms.
Atlassian Support has even accepted requests to enable the Proforma Forms menu for use with JSW for entire instances/orgs, for a while now, so why would this be passed by and even risk being removed completely? We have this enabled and don't need to hack the URL, the menu is there already:
Would Atlassian really remove this, after enabling it for so many customers, and after allowing it to be used for so long?
You can see from the responses here, that many people would prefer the Proforma Forms functionality in "Jira", which is much more complete.
@Christof Hurst Proforma forms capabilities are indeed a really good choice, I do like the fact that we can reduce the number of CF needed as the forms are way more customizable.
Hey ! I'm not sure to understand how we can allow the users that should fill the form content to find the form by themselves in the project view?
It seems we need to send them out of the Jira project.
I'm actually joining comment from Ricciardo Gomes, the effort should mainly be put to on on simplifying the ticket creation panel instead of creating new ways to create tickets...
One more option with Open access could be to allow users having Managed Domain enabled to be able to log an issue if they below to the same Managed Domain - For unlicensed users
Allow public access - [Maybe only to people who have the specific form link] as well as restrict max how many forms can get created to avoid possible security issues - like max forms per day or per hour.
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 hoped that this would solve a few problems for us, but the current implementation is quite useless
We have fairly open Jira projects where everyone can view project content and create tickets (requests) for different teams. There is no need to make everything super restricted.
What would be nice:
allow us to use forms on the "Create Issue" screen.
add a feature to hide other issue types from everyone who doesn't belong to the project team. This way, we could create a "Request" issue type and use a form to intake new requests. It would also be good to have a separate queue/list for these requests.
Scriptrunner is helpful to create workarounds, but you can do better Atlassian.
I don't see any reason to complicate request intake using Jira Service Management when we are one team. That system is more suited for customer requests.
No one is looking for a feature that requires copying and pasting URLs to send them to people for completion.
Jira Software doesn't still have good request intake feature.
We just got forms available on our site and I'm surprised to find out there isn't any sort of pre-fill for the fields. When can we expect this feature to be included in forms so we don't have to keep using the clunky URL method of starting a create issue with fields pre-filled? We were all excited for this forms, but without pre-fill, it's still not helpful for us.
An alternative would be to allow the block descriptions have more than 255 characters and better text formatting so we can guide our users on how we would like them to format the description field in particular.
Okay, so I just read the comments above from @Michiel Schuijer about Proforma and I've gone from slightly annoyed to really pissed off. It has everything we've been looking for and have been paying for with an add-on! So I've got questions for Atlassian now that I don't really expect to get answers to.
How long has this feature been available, behind a "hidden" URL to access?
Why hasn't this been communicated to consumers?
Why would it even cross anyone's mind to get rid of it?
Why are you bothering making any other sort of forms feature instead of just pushing this out to people?
Why have you kept this from us and steered us to paying for this exact feature through an add-on that costs money, took months and many person-hours involving security, finance, legal, and our development teams to trial, vet, and contract?
Hi @Loretta Brunette - thanks for the update. Perhaps a silly question, but will access to this Forms feature only be for those with Atlassian/Jira accounts or can people without accounts complete a form? The reason I ask is because we currently use RaleyForms for externals (or internals without an Atlassian account) to add a request which in turn to converts it into a Jira ticket. Is this functionality something you're looking at within Forms also (the interface is much better and I'd much prefer to use this and stop paying for Raley! :) Thanks Jules
Sorry, but this version of Jira forms is a non-starter. In fact, I wouldn't want any further development on this version, as we would never use them! Why would we introduce a third, entirely different way to create "forms" to our users!!!! Instead, just make the JSM forms the ONLY form tool and be done with it. Allow them to be used when a user selects the create button for any Jira project. Sorry to be so negative, but this is frustrating.
100% agree with @Bill Goetz as we will never use this new version of Jira forms either. JSM forms are way better and make way more sense for our workflows also.
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 can't understand why we need to reinvent the wheel.
Our problem is simple: we don't have an effective request intake process for Jira Software. The new solution is half-baked until it is possible to use a form on the Create screen and make sure that the requester can only use the issue type with the form to submit the request.
The problem I see with this is that developers may need to have multiple forms, and no one wants to have dozens of issue types in their projects.
Workarounds:
1. Grant everyone permission to create tickets in projects. The issue with this is that users often don't know which issue type to use, leading to missing details that are needed to resolve the request. This means we have to follow up multiple times to get all the necessary information.
2. Use Jira Service Management and buy extra licenses just to handle requests from internal users. The problem with this approach is that everyone needs a license to communicate with the requester, making it an impractical and inefficient solution.
Why can't we use the existing forms functionality and make it work for internal users only? This would reduce the impact on Jira Service Management.
64 comments