Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-32906

Can't create JIRA issues from Confluence if a mandatory custom field has types textfield, textarea, number etc

XMLWordPrintable

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

      When creating JIRA issues on Confluence, only support System fields. As such, we then could not create a Jira ticket from Confluence for Jira projects with required/mandatory Custom fields (which have these field types; textfield, textarea, URL, number i.e. Epic name and Epic Link).

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

            [CONFSERVER-32906] Can't create JIRA issues from Confluence if a mandatory custom field has types textfield, textarea, number etc

            James Whitehead added a comment -

            A fix for this issue is available in Confluence Server and Data Center 8.3.0.
            Upgrade now or check out the Release Notes to see what other issues are resolved.

            James Whitehead added a comment - A fix for this issue is available in Confluence Server and Data Center 8.3.0. Upgrade now or check out the Release Notes to see what other issues are resolved.

            Niklas Kordasch added a comment -

            upvote

            Niklas Kordasch added a comment - upvote

            Janet added a comment -

            I guess enough people just gave up on this and are using another product to do this oh like SmartSheet which integrates seamlessly with Jira.  But not Confluence... this is a bug and its absurd they have not fixed this yet.

            Janet added a comment - I guess enough people just gave up on this and are using another product to do this oh like SmartSheet which integrates seamlessly with Jira.  But not Confluence... this is a bug and its absurd they have not fixed this yet.

            Jarek Krochmalski added a comment - - edited

            it means that if you have a mandatory custom field of type other than simple string (like a list for example), the whole Confluence->Jira integration is simply useless.

             

            If you put the price of Jira and the price of Confluence on top of that, it's just ridiculous.

             

            Also, this should not be a "Suggestion", it's a bug.

            Jarek Krochmalski added a comment - - edited it means that if you have a mandatory custom field of type other than simple string (like a list for example), the whole Confluence->Jira integration is simply useless.   If you put the price of Jira and the price of Confluence on top of that, it's just ridiculous.   Also, this should not be a "Suggestion", it's a bug.

            Arne Goderstad added a comment -

            As Atlassian suite admin I get complaints often from my division of why they can't create tasks from confluence pages. And it is because we have custom required fields when creating issues in jira.
            Even 3rd party software is able to accommodate this. We are using SmartBear Collaborator review tool, and when creating jira issues from within Collaborator it queries the REST API and presents all the fields we need.

            Arne Goderstad added a comment - As Atlassian suite admin I get complaints often from my division of why they can't create tasks from confluence pages. And it is because we have custom required fields when creating issues in jira. Even 3rd party software is able to accommodate this. We are using SmartBear Collaborator review tool, and when creating jira issues from within Collaborator it queries the REST API and presents all the fields we need.

            Oryan Rotem added a comment -

            This is a must, we can't use the integration without it, it becomes irrelevant... please implement! 

            Oryan Rotem added a comment - This is a must, we can't use the integration without it, it becomes irrelevant... please implement! 

            zaharovvv@suek.ru added a comment -

            This is base functionality of integration. Big omission.

            zaharovvv@suek.ru added a comment - This is base functionality of integration. Big omission.

            lauramhubbard added a comment -

            Agree - it makes the product requirements portion of confluence practically useless if you can't then turn them into Jira tickets.

            lauramhubbard added a comment - Agree - it makes the product requirements portion of confluence practically useless if you can't then turn them into Jira tickets.

            Gobinath Thiyagarajan added a comment -

            Hi Team, 

            The completion of this integration is essential for our customers when they want to create Jira issue from Confluence. Confluence does not display mandatory/custom fields from confluence macro. 

            Problem: 

            Confluence does not show custom fields while creating an issue from confluence macro. 

             

            Gobinath Thiyagarajan added a comment - Hi Team,  The completion of this integration is essential for our customers when they want to create Jira issue from Confluence. Confluence does not display mandatory/custom fields from confluence macro.  Problem:  Confluence does not show custom fields while creating an issue from confluence macro.   

            Stefan Bittner added a comment -

            Another three and a half year old problem that is not assigned to somebody at Atlassian although it is a real problem. Please read this issue. If you do not change anything it is not possible to create a Jira-issue out of Confluence just because you work with Tempo Timesheets! Unbelievable how you don't see the easy but deep problems!!!

            Stefan Bittner added a comment - Another three and a half year old problem that is not assigned to somebody at Atlassian although it is a real problem. Please read this issue. If you do not change anything it is not possible to create a Jira-issue out of Confluence just because you work with Tempo Timesheets! Unbelievable how you don't see the easy but deep problems!!!

              a9293dbdc671 Thomas Rogozinski
              tvu TruongA
              Affected customers:
              171 This affects my team
              Watchers:
              137 Start watching this issue

                Created:
                Updated:
                Resolved: