Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-65329

Project Link shows Confluence Change Log activity in Unrelated Issues

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Low
    • None
    • 7.3.6, 8.8.1, 8.11.1
    • Application Links
    • None
    • 7.03
    • 8
    • Severity 3 - Minor
    • 0
    • Hide
      Atlassian Update – 12 February 2020

      Hi everyone,

      After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out.

      Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy.

      To see what the Jira team is currently working on and has recently delivered see the following dashboards:

      We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments.

      Thank you,
      Jira Server Bug Fix team

      Show
      Atlassian Update – 12 February 2020 Hi everyone, After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out . Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy . To see what the Jira team is currently working on and has recently delivered see the following dashboards: Jira Server and Data Center: Recently resolved issues Jira Server and Data Center: Current work and future plans Jira Server and Data Center: Bug Fix Board We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments. Thank you, Jira Server Bug Fix team

    Description

      Summary

      When some issues in a JIRA project are included in a Confluence Change Log page, and there's a project link between the JIRA project and the parent Confluence space, the activity of the Change Log creation is shown in the Activity tab of all issues in the JIRA project.

      Steps to reproduce

      1. Create an applinks between JIRA and Confluence
      2. Create a Project Link between JIRA project (PROJ) and Confluence space (SPACE)
      3. Create version 1.0 and issues PROJ-1 -> PROJ-10 in PROJ
      4. Add 1.0 as Fix Version/s to PROJ-1 -> PROJ-5
      5. Create a JIRA Report of type Change Log in SPACE -> Select PROJ and 1.0 as project and version respectively

      Expected behavior

      The activity of the Release Notes creation is only visible in the Activity tab of issues PROJ-1 -> PROJ-5, which are included in the JIRA Report.

      Actual behavior

      The activity of the Release Notes creation is visible in the Activity tab of all issues in the project (PROJ-1 -> PROJ-10 in this example).

      Notes

      If the Project Link is removed, the activity is not shown in any issue, thus there's no way to know from JIRA if an issue is included in a Confluence Change Log. The Suggestion for this is JRASERVER-65332.

      Attachments

        Issue Links

          is incorporated by

          Suggestion - JRASERVER-65332 Ability to know if a JIRA issue is included in a Confluence Change Log page

          • Closed

          Activity

            People

              Unassigned Unassigned
              vdung Andy Nguyen (Inactive)
              Votes:
              9 Vote for this issue
              Watchers:
              15 Start watching this issue

              Dates

                Created:
                Updated: