Open issues

Order by Priority
  1. Suggestion
    JRASERVER-78921Set recipients in To header as well when sending security alert mail
  2. Suggestion
    JRASERVER-4619Custom Fields not displayed in emails
  3. Suggestion
    JRASERVER-20138Removing system fields from the view issue screen.
  4. Suggestion
    JRASERVER-40711Add the possibility to edit Jira error pages
  5. Suggestion
    JRASERVER-42311Preserve embedded images and font formatting in emails to JIRA
  6. Suggestion
    JRASERVER-45296Allow Inline Attachments from Incoming Email appear in JIRA
  7. Suggestion
    JRASERVER-60841Implement report for tracking time in status in JIRA
  8. Suggestion
    JRASERVER-62850Update Confluence Links In JIRA Automatically Based On The New Applink Configurations
  9. Suggestion
    JRASERVER-65027Options to automatically make all Public filters and dashboards to Logged-in users
  10. Suggestion
    JRASERVER-65521Add possibility to disable public access to JIRA
  11. Suggestion
    JRASERVER-66554SAML redirection from Jira Dashboard page or any page other than login.jsp
  12. Suggestion
    JRASERVER-66660Provide the ability to edit the default priority scheme
  13. Suggestion
    JRASERVER-67647Ability to have user session replication between the nodes in Jira Data Center (DC)
  14. Suggestion
    JRASERVER-71975Make Jira and other Atlassian self-hosted products FIPS 140-2 compliant
  15. Suggestion
    JRASERVER-72112Provide the ability to reuse a project key once its original value is altered
  16. Suggestion
    JRASERVER-76926Update Bundled Tomcat and Java versions documentation for Jira 9.12
  17. Suggestion
    JRASERVER-77546Option to export data from App Usage for Jira plugin
  18. Suggestion
    JRASERVER-78567Allow session timeout to be configured by group
  19. Suggestion
    JRASERVER-78660Enhance Jira 10's User Search Endpoint to Return more than 100 Results
  20. Suggestion
    JRASERVER-78689Update Init Container to Import Additional Certificates to OS CA-Certificates
  21. Suggestion
    JRASERVER-78774Provide settings to enable auto close of alert dialogs, and specify timeout values
  22. Suggestion
    JRASERVER-78917CSS for .notify.info is styled with red bold background color, making it difficult to read the text message.
  23. Suggestion
    JRASERVER-34307Add the ability to export/import a single project
  24. Suggestion
    JRASERVER-34945Provide the ability to reuse the project key from a deleted or renamed project
  25. Suggestion
    JRASERVER-36400As a user, I would like translated statuses to show up in the Read-only workflow popup
  26. Suggestion
    JRASERVER-61024Allowlist and Blocklist attachment type in Jira
  27. Suggestion
    JRASERVER-66708Provide the ability to add another quick filters section to the board
  28. Suggestion
    JRASERVER-68153Release next-gen projects in Jira Server
  29. Suggestion
    JRASERVER-69036Escape code on Description field when exporting to CSV
  30. Suggestion
    JRASERVER-69311Ability to have the Websudo functionality working with SAML / SSO
  31. Suggestion
    JRASERVER-72717Jira should remove old jar files of plugins from the shared home as part of an upgrade task when using ZDU
  32. Suggestion
    JRASERVER-73372Ability to check users log in history
  33. Suggestion
    JRASERVER-76527Support for PostgreSQL 16
  34. Suggestion
    JRASERVER-78568Support for Postgres17
  35. Suggestion
    JRASERVER-2734Display last comment in issue navigator column
  36. Suggestion
    JRASERVER-6851Allow more than one custom field context to be associated with the same project but different issue types
  37. Suggestion
    JRASERVER-11405Allow to change the fonts and their size
  38. Suggestion
    JRASERVER-23038Search for Labels using wildcards
  39. Suggestion
    JRASERVER-27539JQL queries that vary by day of the week
  40. Suggestion
    JRASERVER-42122REST API Access Permission
  41. Suggestion
    JRASERVER-43782As an admin I would like to get 'Last login' details using REST api so that I can deactivate users who havn't logged in recently
  42. Suggestion
    JRASERVER-65844Add ability to filter Users by Directory
  43. Suggestion
    JRASERVER-65924Resolutions per issue type
  44. Suggestion
    JRASERVER-70140Increase number of clauses for Smart filter under Rich filter
  45. Suggestion
    JRASERVER-71357Implement SAML Single Logout (SLO) for Jira
  46. Suggestion
    JRASERVER-1391Provide the ability to rename groups after creation
  47. Suggestion
    JRASERVER-15260Add ability to subscribe dashboards
  48. Suggestion
    JRASERVER-16325Customise Issue Links per project
  49. Suggestion
    JRASERVER-27868Provide the ability to migrate users from one directory to another
  50. Suggestion
    JRASERVER-40049Allow translation of custom field options
Refresh results
1 of 7907
Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-78921

Set recipients in To header as well when sending security alert mail

    • 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.

      It seems currently security alert mail will be send only via bcc header.
      The user may receive like below (no To header). 

      To: Undisclosed recipients:;

      It looks strange and customer may if this is a trustful mail or not.

      There is a similar JAC ticket for confluence as well.
      CONFSERVER-99150

            Rick Li created issue -

              e31e1da5babe Randy
              rli@atlassian.com Rick Li
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: