This is a terrible solution from the Atlassian team, I'll stop watching this issue because I'm tired of receiving bad news on my email. Goodbye everyone.

I'm very disappointed and flabbergasted that this is not implemented, and instead a far worse 'forms' has been made available.
Unbelievable and unusable to put it mildly, this Jira Work management forms. I would have thought the cramped and limited JWM features would be dropped where possible and make way for proper functionality, like the Proforma Forms...

This is so bad for us. We are using now the JSM Forms (Proforma) in the majority of our software projects. It works for us. 

The forms that you are implementing now does not to have form field that not linked to a custom field. In this case, we will need to create a lot of fields which will lead to bad performance in our site.

Very bad solution from Atlassian!!!!!!

>"I am excited to share that we are bringing the forms available in business projects to software projects, as well as other enhancements, including conditional logic. The decision to extend business forms instead of the forms available in service projects was made due to a range of factors, including alignment between business and software projects as we move to one Jira."

I voted for this Request because our goal was to integrate JSM information with 3rd level team projects. This worked well with enabling the "dark feature". 

But .. after already making advanced forms available to us, you now cripple them again? Why not make JSM forms available instead and throw the JWM forms completely out? Sooner or later the WM forms will resemble the advanced editing of JSM forms anyway. Simply because your new approach does not take care of the JSM customers. 

Hi 190b4dd3c5b7  - what does this mean for Business projects that are already using the "JSM" forms? Will organizations lose that functionality? Or will those be "grandfathered in"?

We are preparing to expand our use of JSW projects across the organization, however, the largest blocker right now is the request options are extremely limited. Without Jira Forms we are unable to use any dynamic fields or make the process easier for our users. Adding Jira Forms to JSW would be a huge value add and increase the overall use of JSW across our organization.

Customers also want the features and robustness of the CM form to be avail in TM projects

Can you please provide an update on the status of this ticket? It is a critical feature for employees of both Latitude AI and Ford to be able to edit forms in Jira Software projects. This is a major blocker for us.

The Forms feature is already available in Jira Software - and it is the more powerful Forms from Jira Service Management that is available (eg. multi-columns, conditional sections) rather than the limited version of Forms that is available in Jira Work Management.

There was a comment earlier in this thread which I looked into and it turns out it is 100% correct!

from Evan Underwood-Harley added a comment - 07/Nov/2023 3:09 PM
If you raise a support ticket on Atlassian they will turn on the Form feature for Jira Software projects, so you don't have to use the direct URL: https://YOURDOMAIN.atlassian.net/jira/software/c/projects/PROJECTNAME/settings/forms/

I asked Atlassian Support enable the Forms menu option in our Jira Software site, and it is now accessible as a menu option under Project Settings. Atlassian also confirmed that enabling this "hidden" feature has no adverse impact and does not invalidate our support/warranty cover.

Point 1

Now that "Jira Work Management is now part of Jira" has been announced, this would mean Forms should become available for JSW, right?

Point 2

There is still a very good use case for having forms available to be added to JSW issues, because it saves a world of complexity and work when you can simply allow self-service form creation and addition or do this for people as a Jira Admin, instead of the hard to maintain custom fields option (creation/maintenance/performance impact/etc.) and screen management (adding fields/field options/contexts/tabs/etc.).

Point 3

The mentioned update has still not happened, almost a year later:
Update May 2023
At the moment there are no plans to release forms for JSW; however, we will continue to review the demand for this feature and will provide another update in October 2023.

https://getsupport.atlassian.com/browse/PCS-286529

@Michiel this is a form which can be used to create issues. You can copy the link to this form and share with users to complete, then creating the new issue with required fields. The form is then attached to the issue that's been created. 

Hope this helps!

@Bryan Meyerovich and @Matt Coker,

Does this mean the form is (now) available right from the creation of an issue for you, or only after an issue has been created to add it then?

I would like and expect to have a form available right from creation, because once an issue has been created, how many people will pick up on it that there is an extra form to fill? I wonder what way of working you use if adding the form(s) after the issue has already been created.

We now also have forms in JSW and are trying it out to see how we can benefit from this. One feature related to forms that would be very very handy that we have in JSM is that we can add a form to an issue where we gather more information in a structured way. This is something we have found very useful in addition to using forms in JSM and in some cases it would be useful to do the same thing in JSW.

I followed Bryan Meyerovich's advice and now I have forms working in my JSW org. It was very easy to follow the steps

This would really be beneficial for Jira software cloud as there really are not that many alternative add ons that compare to the capabilities of this one.

This is a very important feature to be added

This is available now. You have to contact support and ask them to turn it on for you. If the support guy says it isn’t then u just point them at this ticket and tell them to ask the escalation team, or contact another support person who’s already been filled in. First support person I reached didn’t know about it either till I pinged our sales rep and then a few days later the support person emailed back apologizing lol. They also have project specific priorities now, we had them turn them on too. Side effect though it reset the default priority across all projects, keep an eye out. 

This would be a very helpful addition to Jira Software. Currently, we use clunky third-party apps that is very limited in features and are very slow. Please add Forms to the Software projects ASAP

I am hoping Atlassian sees the value in this.  I have been talking to my CSM about this.  As much as I don't want to admit this, but Asana seems to be much more advanced in this space: Forms – Asana Help Center.  We need atleast the same functionality as a major competitor.  What I am being told is that more of the focus is put on building Forms in Jira Service Mangement vs using the forms in Jira Work Management.  I guess I will have to look into this, but to roll a whole new product seems excessive. 

Mauricio Franzoni

OR Simon | JSM Principal Product Manager

• Is there technical limitations to being able to implement this?
• With this already built out in JSM, I'm curious if the code is reusable?

I understand wanting to "gather interest", however, every team i've worked on or consulted with in the last decade has considered this a point of contention for whether or not to use Jira, as posted by @Thomas Feely, "there doesn't appear to be much interest as the majority of your customer base have likely given up on getting a feature they thought would have obvious need and demand across your entire product suite many, many years ago." 

There is some form of irony in all this, internal Atlassian teams including yours are using a guided intake mechanism allowing individual to create tickets and gather interest for a ticket, why block that as an opportunity for Software Teams (including Product personnel) to use such a valuable feature?

Anyway, this ticket (like most i follow) and note take care at all from Atlassian.. only keep it there .. for hope.. that will never came !

In the other word, they will increase their fee every year.. it's hard to support ticket that will never been took into consideration.

Actually, they will. I've gotten the feature activated just this week via Support team. Thanks Evan, btw!

No Evan, no they won't, but they will tell you it's not available and point you to this ticket, lol

If you raise a support ticket on Atlassian they will turn on the Form feature for Jira Software projects, so you don't have to use the direct URL: https://YOURDOMAIN.atlassian.net/jira/software/c/projects/PROJECTNAME/settings/forms/

I've only been wanting a similar feature to this in Jira Software since I started using Jira about 13 years ago. I imagine if you investigated this you'd find there doesn't appear to be much interest as the majority of your customer base have likely given up on getting a feature they thought would have obvious need and demand across your entire product suite many, many years ago.

I don't have permission to transition this to "In Progress" can I be granted access?

Where's our October update? Or are you leaving it for the 31st as a scary surprise you might actually implement it?

Seems natural to have released FORMS in any and every project product within Atlassians portfolio. Welp, not for Atlassian I guess. Warding this in hopes that it gets released

This is a real conundrum for us: 

If you want Forms with conditional fields you must use JSM, so that is what I did, but it appears they felt no one would want sub tasks on JSM team managed projects? So you cannot have multiple people contribute work to one task, if you want to use conditional forms? What logic was employed to determine any relationship between these things, as being a use case that would never happen? 

It's happening to me right now....

I bought some crystals to help manifest this request into existence 

I'd be really curious to hear an explanation of why someone thought this wouldn't be useful in every type of project product.

Really need this feature. Any update? 

I do find ERIK GAUDIN's solution very interesting but I consider this rather a bug than a feature as this is not equal to forms in JSW, JSM. 

I can create a form that way but I can't use it to create issues.

Even if I edit settings to create Task issue type with the form, it actually doesn't work. 

I can add the from to already created issue which is interesting. So at least I can use forms in JSW project in that way. Might be useful.  

This is certainly much required functionality. There are lots of scenarios where you would like members of other teams to be able to submit information in a very structured way into an issue. It also clearly helps when automating actions and responses, so please consider adding this functionality.

As mentioned in this thread, you can already use forms on Jira Software Projects, you just need to go to the magical hidden setting page.  This isn't rocket science.  Please just enable this. 

I have a hybrid development team that supports planned software development on a scrum schedule AND interrupt work from across the business.  I need the business team to enter in requests in standard forms.  I would prefer not to run multiple boards for the team.

My team use this add-on for Jira https://marketplace.atlassian.com/apps/1227085/smart-jira-forms?tab=overview&hosting=cloud

It works with Jira Software, Jira Core, and Jira Service Management.

And also there is a feature that helps to create new Jira issues based on forms responses https://saasjet.atlassian.net/wiki/spaces/SAASJET/pages/2510454789/Create+a+Jira+issue+based+on+the+submitted+form

I have a team that splits it's time between interrupt driven requests and software development tasks.  Having the ability for those incoming requests to be routed through forums would be exceptionally helpful.

This is a must have feature!! urgently needed!

+1 

Running into use cases for this functionality weekly

We "solved" this by cobbling together a google form and zapier automation, but it is super clunky to have to do it that way.

It's wild to me that this is seen by Atlassian as not being useful for some reason. Most software teams today work within net new + support based contexts, so not allowing forms in JSW is mind blowing to me. It is so incredibly limiting to assume that teams are either/or and the response that it has no plans is frustrating and shows a lack of customer understanding.

While waiting, i'm using this trick (posted on this thread fiew month ago)

I open this URL

https://YOURDOMAIN.atlassian.net/jira/software/c/projects/PROJECTNAME/settings/forms/

That made a Form Page apear for that project. The "Form" in JSW is much better than the one i found in JWM

But i would like to have those "FORM" exposed in a menu, instead of grabing them with this method

Forms are a much needed functionality in JSW! But the use of forms is now very limited, since forms are only available in JSM projects. Colleagues ask why we cannot make a similar interface for users who are not members of the Service Management project, but are licensed by the Software( This would greatly increase the functionality of the Jira Software, not only JSM.

We kindly ask you to reconsider the last decision and, if possible, take it to work.

The comment there from Product Manager, is clear..it's a nice respond to provide instead of "we have no plan, and no interest, providing that feature"

Let's hope they will change their mind in October... but i doubt it.

How has it taken you a year to provide such a poor response to this request? 

Hi Simon!

Thanks for your update!

Very sad to hear this.

This is the 3rd most voted suggestion you have now and it already has 442 votes in 1 year. I don’t remember such a speed of voting on other stories, so the demand for this functionality is as high as possible.

Agreed. I shouldn't have to change my teams workflow to take requests. You are competing with Aha! Roadmunk, google and others just to do a simple task that you could build as a cost plus feature for your customer base. This is low hanging fruit. 

Thanks Samuel. Improving on my product suggestion: keep the "Edit Issues" project permission to Submit forms and modify issue values. Have a new Form setting that lets forms be locked after submitting by users with the "Resolve Issues" project permission.

Instead of:

When submitting:

• Lock form so that only project admins can reopen it 

Have:

When submitting:

• Allow the form to be locked. Tooltip: Only project admins can reopen locked forms.
• (Disabled until the previous toggle is checked) Automatically lock the form. Tooltip: Only project admins can reopen locked forms.

The new process:

When the "Allow the form to be locked" setting is toggled on but not the "Automatically lock the form" setting, the current flow continues until the form is submitted:

1. The assigned Developer adds a form to the issue and fills in what they think the User needs.
2. The User does not have the "Edit Issues" project permission. They cannot edit or submit the form.
3. The Developer submits the form. Linked Jira fields are edited.

The new process:

1. Both the Developer and the User has the "Resolve Issues" project permission. They can either "Reopen" or "Lock" the form.
2. The user reviews the form and, if they agree, clicks “Lock”.
   1. If they disagree, they can "Reopen" the form and add comments to the issue.

The team's way of working is to not proceed with the task until the submitted form is "Locked" by the User. This is easily tracked through "Submitted Forms" and "Locked Forms" custom fields.

Locking and Reopening forms should not edit the issue so shouldn't require the "Edit Issues" project permission. The "Resolve Issues" project permission has no other purpose on its own.

This would be great, we've had to 'hack' together integration between JSM and JSW and tried to sync statuses etc for it.

Advocating for a customer where Forms features borrowed from Jira Service Management are used in a software project but no users/groups/roles are assigned the Edit Issues permission due to their special business needs. Forms added manually to the issue can't be edited regardless of the state.

Let users with the “Resolve Issues” project permission accept forms in the “Open” state.

The process:

1. The assigned Developer adds a form to the issue and fills in what they think the User needs.
2. The User doesn’t have the “Edit Issues” project permission. They can only view the form.
3. The User has the “Resolve Issues” project permission. Instead of a “Submit” button, they see an “Accept” button.
4. The user reviews the proposed changes in the form and, if they agree, clicks “Accept”.
   1. There is no “Decline”, it’s expected that the User reaches out to the Developer to make changes to the form.
5. The changes to issue values by the form are ascribed to the Developer.

In this process, the custody for editing field values still remains with the Developer, as the “Edit Issues” project permission is required to Add forms and fill in the fields on the form.

It makes sense to use the Resolve Issues permission. A Form is resolved when it changes from an Open state to a Submitted state, and there’s nothing that the “Resolve Issues” project permission can do on its own:

• To actually resolve an issue, the user also needs the “Transition Issues” project permission
• To edit the “Fix Versions” field, the user also needs the “Edit Issues” project permission.

This is a useful feature for Jira Service Management projects too. To have a Jira Software user able to accept a form enables a better flow for time-poor executives to have a form that summarises what the executive needs to know for a Change or Service Request.

As the Jira Software user didn’t “Edit” the issue - that custody remains with the JSM agent - it also meets the product licensing delineation, if that’s what you call the rules for what a Jira Software user can do in JSM projects. The Jira Software user didn’t “Work On” the JSM issue, they “accepted” the form, which is equivalent to Approvals.