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

Create multiple JIRA issues from a table in Confluence

XMLWordPrintable

      Description

      When the user tries to create multiple JIRA issues from a table in Confluence the issue is created in JIRA but is not added in the Confluence’s table. If the user creates the issues one by one they are created in JIRA and correctly added to the table in Confluence.

      Steps to reproduce

        1. Create a project into JIRA
        2. Create a new page in Confluence and add a table to it with 2 columns (Title and Description) and 20 rows
        3. Fill the table with the Title of the issue and it’s description
        4. Highlight the first row and a JIRA macro will pop up
        5. Select Create multiple issues from table, select the project you’re created and the issue type and hit Create

      Expected result
      The issues are created in JIRA and added into the table in Confluence

      Actual result
      The issues are created in JIRA but it did not appear in the Confluence’s table

      Workaround

      Create issues one by one

        1. 20171024 step-01.png
          17 kB
        2. 20171024 step-02.png
          26 kB
        3. 20171024 step-03.png
          93 kB
        4. 20171024 step-04.png
          64 kB

            [CONFCLOUD-54612] Create multiple JIRA issues from a table in Confluence

            Keara Stratulat added a comment -

            It would be great if I could also add AC to the Jira ticket this way, too.

            Keara Stratulat added a comment - It would be great if I could also add AC to the Jira ticket this way, too.

            Paul Bury added a comment -

            Installed the latest Confluence upgrade and this broke. It worked before that upgrade for us.

            Paul Bury added a comment - Installed the latest Confluence upgrade and this broke. It worked before that upgrade for us.

            Angelo Gallarello added a comment -

            Any news on this?

            Angelo Gallarello added a comment - Any news on this?

            Kate West-Walker added a comment - - edited

            This bug is tracked by CONFCLOUD-35077. You can go over and follow that issue for updates. I'll be closing this one and linking the two, but reposting our public statement for visibility:

            Hi all,

            My name's Kate - I'm the developer on Confluence who's been looking into this. I'm sorry - I know this is causing you a lot of pain and I wanted to give you a quick update.

            Without getting too technical, we can't fix this problem right at this moment because of some infrastructural changes that are occurring inside Confluence. We do definitely want to fix this, and we will do it as soon as we finish with those changes. We'll keep you updated as we go, so you'll know when we fix it.

            Until then, I do have some other ways in which I can help alleviate some of the pain. First, you can minimise the likelihood of this bug occurring by only using it on a page that doesn't already contain other macros. The size of the table isn't particularly important. Failing this, the main work around is to manually paste the created JIRA issues into the table.

            To clarify (in response to some of the comments), this bug does not relate to performance or time outs, and the JIRA issues are created in JIRA, they're just not added to Confluence.

            Thank you for your understanding.

            Kate

            Kate West-Walker added a comment - - edited This bug is tracked by CONFCLOUD-35077 . You can go over and follow that issue for updates. I'll be closing this one and linking the two, but reposting our public statement for visibility: Hi all, My name's Kate - I'm the developer on Confluence who's been looking into this. I'm sorry - I know this is causing you a lot of pain and I wanted to give you a quick update. Without getting too technical, we can't fix this problem right at this moment because of some infrastructural changes that are occurring inside Confluence. We do definitely want to fix this, and we will do it as soon as we finish with those changes. We'll keep you updated as we go, so you'll know when we fix it. Until then, I do have some other ways in which I can help alleviate some of the pain. First, you can minimise the likelihood of this bug occurring by only using it on a page that doesn't already contain other macros. The size of the table isn't particularly important. Failing this, the main work around is to manually paste the created JIRA issues into the table. To clarify (in response to some of the comments), this bug does not relate to performance or time outs, and the JIRA issues are created in JIRA, they're just not added to Confluence. Thank you for your understanding. Kate

            julia_tsai added a comment - - edited

            Hi, 

            Just want to know that below problem is normal?

            Highlight a text section on Wiki then mouse right click to create a Jira ticket is a legacy feature. I can’t use this feature to create ticket not only on new Jira project but existing projects. (see attachments step-01 and step-02)

            When I edit the page, click '+' and choose JIRA Issue/Filter, I could create a new JIRA ticket. (see attachments step-03 and step-04)

            Please help to check, thanks.

            julia_tsai added a comment - - edited Hi,  Just want to know that below problem is normal? Highlight a text section on Wiki then mouse right click to create a Jira ticket is a legacy feature. I can’t use this feature to create ticket not only on new Jira project but existing projects. (see attachments step-01 and step-02) When I edit the page, click '+' and choose JIRA Issue/Filter , I could create a new JIRA ticket. (see attachments step-03 and step-04) Please help to check, thanks.

              Unassigned Unassigned
              cmeireles Charles Meireles
              Affected customers:
              12 This affects my team
              Watchers:
              25 Start watching this issue

                Created:
                Updated:
                Resolved: