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

Issue Collector: Default values for name/email overrides real (logged in) user's identity

    XMLWordPrintable

Details

    • 6.04
    • 1
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 06 November 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 – 06 November 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

      The case:

      In our apps, where we include collector, we want to set default values for name and email fields, so user does not have to type it by hand. It can be easily done because we have user context within application.

      The problem:

      When user is logged in to Jira those default values overrides real user's identity, so issue's reporter would be set based on name/email fields, not on user's Jira session.

      In our organization each user has many email aliases, so it is possible that email from app context will be different to Jira's account email. So finally, if we set default email when configuring collector and user is logged in, but has different email on Jira, we can lose some reliable data because reporter in this issue could be default assignee (default email not matched) instead of real Jira user.

      Possible workaround:

      It could be possible to bypass this problem if determining user on the JS level (when configuring collector) would be possible. Real data isn't even required, only boolean flag if user has session. I have tried many ways, but most of them are blocked by same origin policy. I also wanted to get user from X-AUSERNAME header (additional request to collector's configuration), but without success.

      Real solution:

      Use Jira's session instead of name/email values passed from collector, especially since clicking "not you" does not allow to provide name and email (JRA-32342 / JRA-38869).

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. JRACLOUD-66658 Cannot change automatically detected user by JIRA Issue Collector form

          • Low - Low priority issues
          • Closed

          Activity

            People

              Unassigned Unassigned
              fdf0d718c106 Grzegorz Korba
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: