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

Issue collector not loading/appear when user has no access to JIRA but has Confluence Access

    XMLWordPrintable

Details

    • 1
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 22 August 2019

      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,

      Pawel Drygas,

      Jira Server Bugmaster

      Show
      Atlassian Update – 22 August 2019 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, Pawel Drygas, Jira Server Bugmaster

    Description

      NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.

      Summary

      Issue collector not loading/appear when user has no access to JIRA but has Confluence (as example) Access.

      Environment

      Instance must have JIRA and CONFLUENCE installed and an issue collector being used. (Tests were made in cloud environment)
      Also, this HTML embedded code bed can be used for testing http://www.csgnetwork.com/htmlcodetest.html

      Steps to Reproduce

      1. Create an issue collector
      2. Assign a proper default reporter
      3. Create a user limited to access confluence only (must not be allowed to access JIRA and)
      4. Log in to JIRA as that user (either logging out and entering that user credentials or using the log "in as user" feature)
      5. Paste the Issue Collector html code in the test site i.e: http://www.csgnetwork.com/htmlcodetest.html and test it.

        Expected Results

      Should be able to open an issue normally using the collector.

      Actual Results

      When using the "log in as user" feature, it shows the issue collector tab, but won't load (stuck on loading wheel). When entering user credentials in confluence, then trying to test the issue collector, the collector tab won't show.

      {noformat}
      ...
      {noformat}
       

      Notes

      Took a deep check and couldn't find any related bug.

      Workaround

      Log out from Atlassian applications before using it, or use access with incognito mode.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              emasiero Eduardo Masiero
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: