• 56
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Atlassian Update - 14 October 2024

      Hi everyone,
      Thank you for your comments on this ticket. We are currently working on supporting additional fields, such as the Parent field, in forms in business projects. I will update this ticket with our support documentation with a full list of supported fields shortly,

      Thanks, 

      Loretta
      Product Manager-Jira Cloud

      Summary

      In form, it shows only some specific fields. As a user, I'd like to be able to support all fields. Because some fields are unsupported, if any of them are mandatory you will get the following error:

      This form contains unsupported required fields, which will prevent respondents to submit critical information. Please contact your administrator to make these fields optional.

      Example: Security Level field, Assets etc

            [JWMCLOUD-29] Ability to support all fields under Forms

            Our primary use case is to allow technical teams to easily raise issues (bugs or risks in our specific case) without needing to use jira, the technical management and PM teams triage the issues and manage locally. Jira reports are used to communicate the bugs and risks etc as a table which allows anyone to filter review easily. The use of custom fields allows us to support automated scripts and filtering of the issue raised in our case the product/system/assembly etc applicable to the issue and the development cycle / test rig etc its linked to.

            Chris Rollins added a comment - Our primary use case is to allow technical teams to easily raise issues (bugs or risks in our specific case) without needing to use jira, the technical management and PM teams triage the issues and manage locally. Jira reports are used to communicate the bugs and risks etc as a table which allows anyone to filter review easily. The use of custom fields allows us to support automated scripts and filtering of the issue raised in our case the product/system/assembly etc applicable to the issue and the development cycle / test rig etc its linked to.

            Hi everyone
            Thank you for your comments on this ticket. I would love to understand more about how you are using Forms in Jira Business projects today and how additional field support (or other features) could improve the value of this feature for your or your team.
            If you can spare 30 mins to chat, please book time in with me here
            thanks
            Loretta - Product Manager, Jira Cloud

            Loretta Brunette added a comment - Hi everyone Thank you for your comments on this ticket. I would love to understand more about how you are using Forms in Jira Business projects today and how additional field support (or other features) could improve the value of this feature for your or your team. If you can spare 30 mins to chat, please book time in with me here thanks Loretta - Product Manager, Jira Cloud

            Jorge C added a comment -

            IT would be nice to be able to add fields on the mobile side - it seems that is not totally handled by "screen" as an example PARENT field is in some weird drop down not really a good user experience, but am greeted with a epic name "no longer is now handled BY PARENT"  yet gives nothing to the user to know ok WHERE IS IT?

             

            Mobile do not have parent field on screen form when editing if there was no parent attached to story.

            Those stories with parent will see it in on the form in a separate area.  There is no way to control where it lands.

            Jorge C added a comment - IT would be nice to be able to add fields on the mobile side - it seems that is not totally handled by "screen" as an example PARENT field is in some weird drop down not really a good user experience, but am greeted with a epic name "no longer is now handled BY PARENT"  yet gives nothing to the user to know ok WHERE IS IT?   Mobile do not have parent field on screen form when editing if there was no parent attached to story. Those stories with parent will see it in on the form in a separate area.  There is no way to control where it lands.

            It would be very beneficial to be able to ad the "Parent" field to forms. Actually the lack of this option is very frustrating... 

            Claus Østergaard Pedersen added a comment - It would be very beneficial to be able to ad the "Parent" field to forms. Actually the lack of this option is very frustrating... 

            I am desperate need of this feature, we want to roll assets out to our entire company and are limited to 300 Service Desk Agent licenses, whilst our Jira user group will be in the thousands. Assets are integrated already into Jira Work Management screens so it only seems logical to extend that to the forms and lists. Please extend Jira Work Management forms to support assets

            Bill.Petridis added a comment - I am desperate need of this feature, we want to roll assets out to our entire company and are limited to 300 Service Desk Agent licenses, whilst our Jira user group will be in the thousands. Assets are integrated already into Jira Work Management screens so it only seems logical to extend that to the forms and lists. Please extend Jira Work Management forms to support assets

            Jonas added a comment -

            Jonathan Smith, I would say basic features "working"...

             

            Jonas added a comment - Jonathan Smith, I would say basic features "working"...  

            Jonathan Smith added a comment - - edited

            Atlassian, please supply an update or assign this ticket.

            Jonathan Smith added a comment - - edited Atlassian, please supply an update or assign this ticket.

            Jonas added a comment -

            Take your time, it´s been more than a year since...

             

             

            Jonas added a comment - Take your time, it´s been more than a year since...    

            This feature would be extremely beneficial to be added to JWM. Currently the limited fields that can be applied to form is not providing the enriched enhancement we would have expected from JWM. In order to get the version we want we would have to set up another project within JSM in order to use JSM more configurable form creation functionality which is not the ideal solution for us considering this is an embed function in JWM.

            Francesca Hart added a comment - This feature would be extremely beneficial to be added to JWM. Currently the limited fields that can be applied to form is not providing the enriched enhancement we would have expected from JWM. In order to get the version we want we would have to set up another project within JSM in order to use JSM more configurable form creation functionality which is not the ideal solution for us considering this is an embed function in JWM.

            Chris Rollins added a comment - - edited

            This feature request is important to us streamlining and encouraging bug and risk raising in our project teams. I have upvoted on the account of having "components" and "affects version" fields available on the forms.

            Chris Rollins added a comment - - edited This feature request is important to us streamlining and encouraging bug and risk raising in our project teams. I have upvoted on the account of having "components" and "affects version" fields available on the forms.

              190b4dd3c5b7 Loretta Brunette
              cfontana@atlassian.com Cristiano
              Votes:
              171 Vote for this issue
              Watchers:
              99 Start watching this issue

                Created:
                Updated: