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

Jira Chart returns duplicate status columns when using a query that returns NextGen and regular projects in Jira

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Low Low
    • Macros - Jira Issues
    • None

      Issue Summary

      • Jira Chart macro duplicate status columns when reporting on NextGen and Software projects, even though both projects use the exact same Status.

      Steps to Reproduce

      1. Create two Jira projects, one being NextGen, while the other being a regular software project.
      2. Populate these two projects with some issues, transitioning them to status "Done", "In Progress" and "To Do". - Both these projects should have the same default statuses;
      3. Create a page on Confluence, and add a Jira Chart macro > Select the "Two Dimensional" option;
      4. Add a filter that would return all issues across both projects (In my case I used ' text ~ "test" ')

      Expected Results

      • All issues that have the same status to be displayed under the same column.

      Actual Results

      • Issues with the exact same status are reported on different columns, as can be seen in this next screenshot.

      This affects both the Legacy and the new editor alike

      Workaround

      • The only workaround would be to add two separate Jira Chart macros, each one reporting just one regular projects, while the other reports on NextGen projects.

        1. Screen Shot 2020-09-04 at 11.35.41.png
          Screen Shot 2020-09-04 at 11.35.41.png
          176 kB

            [CONFCLOUD-70750] Jira Chart returns duplicate status columns when using a query that returns NextGen and regular projects in Jira

            Lingyang Zhu added a comment -

            Hi halegra and everyone,

            This is Lingyang Zhu from the Confluence team. Thank you for raising this bug and bringing it to our attention. After examining this issue, we weren’t able to reproduce the bug related to Jira chart macro within our instances as now Jira chart macros require users to select a Jira project before they can be incerted. To set the right expectations, we are closing this bug to focus on our upcoming roadmap for all Confluence users.

            If this is still an issue for you, please let us know. Thank you again for providing valuable feedback to our team!

            Best,

            Lingyang Zhu

            Lingyang Zhu added a comment - Hi halegra and everyone, This is Lingyang Zhu from the Confluence team. Thank you for raising this bug and bringing it to our attention. After examining this issue, we weren’t able to reproduce the bug related to Jira chart macro within our instances as now Jira chart macros require users to select a Jira project before they can be incerted. To set the right expectations, we are closing this bug to focus on our upcoming roadmap for all Confluence users. If this is still an issue for you, please let us know. Thank you again for providing valuable feedback to our team! Best, Lingyang Zhu

            Djahari Clark added a comment - - edited

            I would like to add that this same bug occurs when you use the pie chart macros - the pie chart will show duplicated status slices when you combine NextGen and Classic projects in the search.

            Djahari Clark added a comment - - edited I would like to add that this same bug occurs when you use the pie chart macros - the pie chart will show duplicated status slices when you combine NextGen and Classic projects in the search.

              Unassigned Unassigned
              halegra Helton A. (Inactive)
              Affected customers:
              3 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: