Open issues

Order by Priority
  1. Suggestion
    JRASERVER-74799Provide features to Integrate ChatGPT with Jira DC/Server
  2. Suggestion
    JRASERVER-66870Allow custom fields of type "Text Field" to be used as the Statistic Type for the "Pie Chart" and the "Two dimensional filter" gadgets
  3. Suggestion
    JRASERVER-79012As a Jira user, I'd like to customize the gadget update frequency and priority
  4. Suggestion
    JRASERVER-74944Include rsync package in JIRA DC Docker images
  5. Suggestion
    JRASERVER-36415Have a Trash/Recycle Bin in JIRA
  6. Suggestion
    JRASERVER-78648Lot of WARN log messages for Method needs allowlisting.
  7. Suggestion
    JRASERVER-72824DVCS docs - Delete Repository
  8. Suggestion
    JRASERVER-72826DVCS docs missing configuration details
  9. Suggestion
    JRASERVER-66863Update the Mail Handler documentation on what is considered a bulk message
  10. Suggestion
    JRASERVER-28458Improve JIRA compatibility with OWASP ModSecurity Core Rule Set (CRS)
  11. Suggestion
    JRASERVER-31227Notification Center
  12. Suggestion
    JRASERVER-33672Improve the way Labels can be deleted in JIRA
  13. Suggestion
    JRASERVER-43296Restrict a label by project
  14. Suggestion
    JRASERVER-60543Restrict the creation of labels
  15. Suggestion
    JRASERVER-64599Issue Created or Issue Updated events are not trapped when importing issues using CSV External System Import
  16. Suggestion
    JRASERVER-65574Feedback on Project Level Administration
  17. Suggestion
    JRASERVER-68550Release Data Center version of Atlassian and Atlassian Labs Jira apps
  18. Suggestion
    JRASERVER-72908Add REST API Endpoint to allow workflow creation
  19. Suggestion
    JRASERVER-74495Allow customisation of the "None" option for select list custom fields
  20. Suggestion
    JRASERVER-78992Jira installers can be downloaded for version 10
  21. Suggestion
    JRASERVER-79021ability to allowlist the Jira Crowd URL when Jira is used as the user directory in Confluence, especially when a PAT is used for authentication, basic authentication is disabled, and full synchronization is failing
  22. Suggestion
    JRASERVER-6851Allow more than one custom field context to be associated with the same project but different issue types
  23. Suggestion
    JRASERVER-21201Dashboard layout should be more flexible
  24. Suggestion
    JRASERVER-28225Mentions of groups
  25. Suggestion
    JRASERVER-43425Configurable size of pie chart
  26. Suggestion
    JRASERVER-66741Allow JQL history search for more issue types (such as the Issue Type field)
  27. Suggestion
    JRASERVER-74434Bring back the ability to display multiple transition buttons in Issues
  28. Suggestion
    JRASERVER-77736Ability to change the order of the Issues in Epic
  29. Suggestion
    JRASERVER-39618A released version should only be selectable from the Affects Version field, not Fix Version.
  30. Suggestion
    JRASERVER-61992Deleting Reciprocal Issue Links on Issues on Remote Jira instances
  31. Suggestion
    JRASERVER-62216Export (CSV, All Fields) and Export (CSV, Current Fields) shows the heading as 'Custom field (<field name>)'
  32. Suggestion
    JRASERVER-20138Removing system fields from the view issue screen.
  33. Suggestion
    JRASERVER-30708Bulk deactivate users
  34. Suggestion
    JRASERVER-47605To-do lists (checkbox) for description field on tickets
  35. Suggestion
    JRASERVER-66849Allow more than one custom field context to be associated with the same project but different issue types
  36. Suggestion
    JRASERVER-71119As a user, I'd like to be able to identify archived issues in issue or epic links
  37. Suggestion
    JRASERVER-72020Limit roles options to the project in users and roles page
  38. Suggestion
    JRASERVER-74418Send email notification when a reaction is added to a comment
  39. Suggestion
    JRASERVER-77809Support sections with different layouts in Dashboard
  40. Suggestion
    JRASERVER-78774Provide settings to enable auto close of alert dialogs, and specify timeout values
  41. Suggestion
    JRASERVER-69311Ability to have the Websudo functionality working with SAML / SSO
  42. Suggestion
    JRASERVER-7211Allow configuration of when issue keys are shown in strike-through font
  43. Suggestion
    JRASERVER-79019The option to link Atlassian Home Goals with Jira DC work items - Goals connector for Jira DC
  44. Suggestion
    JRASERVER-12397Filter Subscription - Notify only when changes appeared
  45. Suggestion
    JRASERVER-61118Possibility to import external web-links from CSV into issue links
  46. Suggestion
    JRASERVER-62571Support for Oracle RAC
  47. Suggestion
    JRASERVER-65638Ability to change color of entire card, not just a color bar
  48. Suggestion
    JRASERVER-67942Local groups should be applied globally over user directories
  49. Suggestion
    JRASERVER-70140Increase number of clauses for Smart filter under Rich filter
  50. Suggestion
    JRASERVER-77509As a Jira administrator I'd like to see the JSON export functionality in a stable version
Refresh results
74 of 7931
Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-28225

Mentions of groups

    • 111
    • 39
    • Hide
      Atlassian Update – 28 February 2018

      Hi everyone,

      Thanks for your interest in this issue.
      This request is considered a potential addition to our longer-term roadmap.

      We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status.

      For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including:

        • Performance and stability improvements
        • Archiving projects for improved performance
        • Optimising the use of custom fields
        • Improving performance of boards
        • Improving Jira notifications
        • Allowing users to edit shared filters and dashboards
        • Mobile app for Jira Server

      You can learn more about our approach to highly voted server suggestions here.

      To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions.

      Kind regards,
      Jira Server Product Management

      Show
      Atlassian Update – 28 February 2018 Hi everyone, Thanks for your interest in this issue. This request is considered a potential addition to our longer-term roadmap. We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status. For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including: Performance and stability improvements Archiving projects for improved performance Optimising the use of custom fields Improving performance of boards Improving Jira notifications Allowing users to edit shared filters and dashboards Mobile app for Jira Server You can learn more about our approach to highly voted server suggestions here . To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions . Kind regards, Jira Server Product Management
    • 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.

      Often times, I'd like to mention an entire group in JIRA rather than individual users.

      Obviously this has the potential to be abused in large instances such as this, but the ability to disable combined with a list of groups that can be mentioned could mitigate these concerns.

      An additional safe-guard may be to limit who can mention certain groups.

        1. image-2017-04-12-12-45-23-523.png
          image-2017-04-12-12-45-23-523.png
          2 kB
        2. JIRA Mention.PNG
          JIRA Mention.PNG
          23 kB

            Juan Ramón Alonso García added a comment -

            +1

            Juan Ramón Alonso García added a comment - +1

            L added a comment -

            +1 

            L added a comment - +1 

            Iryna Muntianova added a comment -

            +1

            Iryna Muntianova added a comment - +1

            Eetu Heino added a comment -

            +1

            Eetu Heino added a comment - +1

            Lisa-Marie Muno added a comment -

            +1

            Lisa-Marie Muno added a comment - +1

            Anthony Romm added a comment -

            +1

            Anthony Romm added a comment - +1

            Aleksandra Leesment added a comment -

            Waiting for any updates!

            Aleksandra Leesment added a comment - Waiting for any updates!

            TH.Kang added a comment -

            +1

            TH.Kang added a comment - +1

            ckent added a comment - - edited

            Hello @Daniel Cosmus, thank you for the creation of your Jira Plug-in app: User Mention Groups for the Richtext Editor, however, the core concern and reason this particular tickets exists (JRASERVER-28225) is because this behavior and functionality should be inherit behavior. It should not require additional costs or extensions.

            This type of functionality is critical to maintaining team communication and coordination and has been an industry standard for these types of Tools / Applications for decades (Microsoft Outlook, Google Gmail), also many products that are direct competitors to Jira, like Monday, Asana, Aha etc. all have this feature by default as well.

            In my opinion, this is a major mis-step my Atlassian for multiple reasons. That said, the big one for me is that this has been a long standing ticket created back in  10/May/2012..., being over a decade old, it clearly indicates that Jira / Atlassian do not care about or prioritize User Feedback and Requests.

             

            That is the problem!

            ckent added a comment - - edited Hello @Daniel Cosmus, thank you for the creation of your Jira Plug-in app: User Mention Groups for the Richtext Editor , however, the core concern and reason this particular tickets exists ( JRASERVER-28225 ) is because this behavior and functionality should be inherit behavior. It should not require additional costs or extensions. This type of functionality is critical to maintaining team communication and coordination and has been an industry standard for these types of Tools / Applications for decades (Microsoft Outlook, Google Gmail), also many products that are direct competitors to Jira, like Monday, Asana, Aha etc. all have this feature by default as well. In my opinion, this is a major mis-step my Atlassian for multiple reasons. That said, the big one for me is that this has been a long standing ticket created back in  10/May/2012 ..., being over a decade old, it clearly indicates that Jira / Atlassian do not care about or prioritize User Feedback and Requests.   That is the problem!

            Yichi Zhang added a comment -

            +1

            Yichi Zhang added a comment - +1

              Unassigned Unassigned
              jhammons Jason C. Hammons (Inactive)
              Votes:
              907 Vote for this issue
              Watchers:
              444 Start watching this issue

                Created:
                Updated: