Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-32906

Allow input JIRA custom field - select list (single choice) if it is a required field when creating JIRA issue

XMLWordPrintable

    • 1
    • 20

    • 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.

      NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.

      When creating JIRA issues on Confluence, only support:
      System fields
      Custom fields which have these field types such textfield, textarea, URL, number (ie Epic name).

      In this ticket we will support JIRA custom field - select list (single choice) if this is required field to input when creating JIRA issues.

          Form Name

            [CONFCLOUD-32906] Allow input JIRA custom field - select list (single choice) if it is a required field when creating JIRA issue

            Carl DiClementi added a comment -

            ^^^ what Jack said. The key value to Confluence is a tight integration with Jira, please continue to improve that integration 

            Carl DiClementi added a comment - ^^^ what Jack said. The key value to Confluence is a tight integration with Jira, please continue to improve that integration 

            Jack Brickey added a comment -

            Very interested in the enhancement. It is very limiting at the moment as we build requirements in a table w/in Confluence and then convert them to JIRA issues via the 'create from table' feature. Unfortunately many of our projects have field requirements like Components that are not currently supported.

            Jack Brickey added a comment - Very interested in the enhancement. It is very limiting at the moment as we build requirements in a table w/in Confluence and then convert them to JIRA issues via the 'create from table' feature. Unfortunately many of our projects have field requirements like Components that are not currently supported.

            Yariv Sheizaf added a comment -

            Hi, Will be very useful for my site Jira-Confluence integrated system

            Yariv Sheizaf added a comment - Hi, Will be very useful for my site Jira-Confluence integrated system

            Ian Baker added a comment -

            This is currently affecting our system with Tempo Timesheets's "Account" field, any feedback on the resolution of the problem ?

            Ian Baker added a comment - This is currently affecting our system with Tempo Timesheets's "Account" field, any feedback on the resolution of the problem ?

            Mário Raodrigues added a comment -

            This on is, really needed, and comes as a request mainly from Managers and Product Owners that have a saying on a go/no-go for JIRA and Confluence 

            Mário Raodrigues added a comment - This on is, really needed, and comes as a request mainly from Managers and Product Owners that have a saying on a go/no-go for JIRA and Confluence 

            Manjusha Deshpande added a comment - - edited

            People are asking for this feature for last 2 years and there is no solid response from Atlassian team. Can you please let us know whether are you planning or at least thinking on this feature ? 

            Manjusha Deshpande added a comment - - edited People are asking for this feature for last 2 years and there is no solid response from Atlassian team. Can you please let us know whether are you planning or at least thinking on this feature ? 

            Ajay Gupta added a comment -

            Is there any update on this, we are willing to upgrade to confluence 6.x and JIRA 7.x as this is critical for us.

            Our BA community want abiility to update all mandatory fields from within confluence.

            ajay

            Ajay Gupta added a comment - Is there any update on this, we are willing to upgrade to confluence 6.x and JIRA 7.x as this is critical for us. Our BA community want abiility to update all mandatory fields from within confluence. ajay

            Justin Nichols added a comment -

            Agreed this would be highly useful!

            Justin Nichols added a comment - Agreed this would be highly useful!

            Yariv Sheizaf added a comment -

            I join to Sona:
            Hi, Atlassian ! We need this feature for integrated Jira-confluence ALM solution. Will you deal with that? Thanks for any feedback

            Yariv Sheizaf added a comment - I join to Sona: Hi, Atlassian ! We need this feature for integrated Jira-confluence ALM solution. Will you deal with that? Thanks for any feedback

            Sona Husakova added a comment -

            Hi, Atlassian ! We need this feature for agile development with using product Confluence. Will you deal with that? Thanks for any feedback!

            Sona Husakova added a comment - Hi, Atlassian ! We need this feature for agile development with using product Confluence. Will you deal with that? Thanks for any feedback!

            Roman Joss added a comment -

            We do have required Customfields in Jira and our Users all would like to use that Feature.
            Please go on with this Suggestion so we also can use the Confluence-Feature to create JIRA Issues....
            Thanks!

            Roman Joss added a comment - We do have required Customfields in Jira and our Users all would like to use that Feature. Please go on with this Suggestion so we also can use the Confluence-Feature to create JIRA Issues.... Thanks!

            Adam Dennett added a comment -

            Any chance this is going to be implemented soon! this is causing us a headache at the minute!

            Adam Dennett added a comment - Any chance this is going to be implemented soon! this is causing us a headache at the minute!

            kristjan_h added a comment -

            Why not make the Confluence create jira ticket window customize-able?

            We have a problem with this because we use Tempo plugin in jira and there we have a required field across all our projects to select the account (we call it Customer Billing Group).
            It is a drop down list, single choice.

            If we are going to edit all our workflows to validate that field instead making it required (by one click in the tempo plugin configuration) we need to go through about 40-50 workflows used by 30-40 projects.
            Please look at this as soon as possible.

            kristjan_h added a comment - Why not make the Confluence create jira ticket window customize-able? We have a problem with this because we use Tempo plugin in jira and there we have a required field across all our projects to select the account (we call it Customer Billing Group). It is a drop down list, single choice. If we are going to edit all our workflows to validate that field instead making it required (by one click in the tempo plugin configuration) we need to go through about 40-50 workflows used by 30-40 projects. Please look at this as soon as possible.

            Marko Malmberg added a comment -

            I second what Wolfgang said. Confluence really should open the exactly same issue creation screen that you have in Jira. Honestly I think without that you really can't say that Confluence and Jira are well integrated. If that can't be done for some reason, then this suggestion here is very important.

            Marko Malmberg added a comment - I second what Wolfgang said. Confluence really should open the exactly same issue creation screen that you have in Jira. Honestly I think without that you really can't say that Confluence and Jira are well integrated. If that can't be done for some reason, then this suggestion here is very important.

            Diamantino Campos added a comment -

            Hi,

            do you have plans for the release of this feature?

            Best regards

            Diamantino Campos added a comment - Hi, do you have plans for the release of this feature? Best regards

            Wolfgang Seidler added a comment -

            I would take an approach, where Confluence displays the Jira Screens, that are defined, as if I would create the same issue in Jira itself (incl. validators/conditions defined in an issue create step). Would make many other new feature requests obsolete

            Wolfgang Seidler added a comment - I would take an approach, where Confluence displays the Jira Screens, that are defined, as if I would create the same issue in Jira itself (incl. validators/conditions defined in an issue create step). Would make many other new feature requests obsolete

            Edgard added a comment -

            Adding the assignee input type field would be great

            Edgard added a comment - Adding the assignee input type field would be great

              Unassigned Unassigned
              tvu TruongA
              Votes:
              89 Vote for this issue
              Watchers:
              69 Start watching this issue

                Created:
                Updated: