• Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • None
    • Email notifications
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

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

      Some customers want to hide Jira from their Customers who lodge support requests though email.
      They want the Customer not to know about Jira but rather interact purely by email.

      The following are some of the problems that the current system has with this:

      1. When a user sends an email they will recieve an email back saying they have an account at Jira and can then log on.
      2. They should most probably be put into a special group. (could be specified in the service)
      3. They can log on to Jira (they should be blocked) I.e. They should have Use permisions but not Log on permissions.
      4. They should receive Notifications without links back to the web pages. (Internal Users should still get the normal ones)
      5. By default these users will receive Notifications made by themselves. The default should be set to False.

      (That is all I can think of for now.....)

            [JRASERVER-8759] Email only interface to Jira

            Hi,

            This is a bulk update to specific issues in the JIRA (JRA) project

            As part of an effort to ensure we are transparent about the JIRA issues on jira.atlassian.com, we have decided to resolve those that have been open for multiple years with minimal activity and with a low number of votes. In light of the fact that JIRA is rapidly changing and that this issue may not be a valid request any longer, we will be resolving it today.

            Votes are not the only metric that we use to determine the requests that are implemented, however they do factor in to our decision making process. We have decided that the combination of this issue being open for a long period of time, and it's low number of votes means that we are unlikely to implement it. If you would like thoughts on how we use jira.atlassian.com, please see: https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com

            If you have believe this issue is still relevant, please comment on the issue and we will respond. We are watching all these issues that we bulk close.

            Best regards
            Roy Krishna and Josh Devenny
            JIRA Product Management

            Roy Krishna (Inactive) added a comment - Hi, This is a bulk update to specific issues in the JIRA (JRA) project As part of an effort to ensure we are transparent about the JIRA issues on jira.atlassian.com, we have decided to resolve those that have been open for multiple years with minimal activity and with a low number of votes. In light of the fact that JIRA is rapidly changing and that this issue may not be a valid request any longer, we will be resolving it today. Votes are not the only metric that we use to determine the requests that are implemented, however they do factor in to our decision making process. We have decided that the combination of this issue being open for a long period of time, and it's low number of votes means that we are unlikely to implement it. If you would like thoughts on how we use jira.atlassian.com, please see: https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com If you have believe this issue is still relevant, please comment on the issue and we will respond. We are watching all these issues that we bulk close. Best regards Roy Krishna and Josh Devenny JIRA Product Management

              Unassigned Unassigned
              nick.menere Nick Menere [Atlassian] (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: