Open issues

Order by Priority
  1. Suggestion
    JSWSERVER-25266JIRA Group as a Team
  2. Suggestion
    JSWSERVER-25120Ability to toggle review option in advanced roadmap
  3. Suggestion
    JSWSERVER-15761Missing status in workflow affecting Agile report
  4. Suggestion
    JSWSERVER-21051Jira and platform support for Windows
  5. Suggestion
    JSWSERVER-16350Make it possible to order Swimlanes
  6. Suggestion
    JSWSERVER-24771Increase the project, issue, and team limits in Plan
  7. Suggestion
    JSWSERVER-26311Inadequate documentation of Velocity template allowlisting after Jira 10.0.X
  8. Suggestion
    JSWSERVER-25116Plan should use Issue Resolution rather than Issue Status Category to determine when to remove issues
  9. Suggestion
    JSWSERVER-9619Support for Scaled Agile framework from Dean Leffingwell...
  10. Suggestion
    JSWSERVER-21346Create GUI or REST interface to manipulate indexed change history fields
  11. Suggestion
    JSWSERVER-8937Improve accuracy of version report and allow to get a gadget
  12. Suggestion
    JSWSERVER-21878Create issue from Ms Team does not show custom fields
  13. Suggestion
    JSWSERVER-24871Support different types of scheduling dependencies
  14. Suggestion
    JSWSERVER-24887Enable feature to correct dependency using auto-schedule in Jira DC instance
  15. Suggestion
    JSWSERVER-26508PI Roadmap: Deactivate automatic lead time consideration for dependency risk evaluation
  16. Suggestion
    JSWSERVER-15276Simplified Workflow: add option to disable the creation of new statuses
  17. Suggestion
    JSWSERVER-16698Add Initiatives View in the Boards
  18. Suggestion
    JSWSERVER-16744Adding custom columns to Release Page
  19. Suggestion
    JSWSERVER-20741Ability to configure quick filters to function as OR searches instead of AND searches
  20. Suggestion
    JSWSERVER-25115Milestones
  21. Suggestion
    JSWSERVER-25159Ability to include the Reporter field in a plan.
  22. Suggestion
    JSWSERVER-25193Release the "duplicate plan" feature for Jira Data Center
  23. Suggestion
    JSWSERVER-25222Export plan as PDF
  24. Suggestion
    JSWSERVER-25225Allow 'Import Issues from CSV' function to populate ARJ Target Start and End date custom fields
  25. Suggestion
    JSWSERVER-20504Allow DVCS account to be automated via REST API
  26. Suggestion
    JSWSERVER-11871As a user, I'd like to know who is the sprints creator
  27. Suggestion
    JSWSERVER-12432In a Filter, I should be able to query for issues closed in the most recently closed sprint
  28. Suggestion
    JSWSERVER-15705Improper Message: A subtask cannot be assigned to an epic
  29. Suggestion
    JSWSERVER-16256Ability to set sprint names longer than 30 characters
  30. Suggestion
    JSWSERVER-21238Support Github Cloud Enterprise organisation managed by Azure IdP
  31. Suggestion
    JSWSERVER-21245Ability to add custom columns in release page (view)
  32. Suggestion
    JSWSERVER-24538Ability to change the date format on an Advanced Roadmap plan in Server / DC
  33. Suggestion
    JSWSERVER-25247Portfolio Team Avatar
  34. Suggestion
    JSWSERVER-26078Add support to MySQL 8.4
  35. Suggestion
    JSWSERVER-16580Document limitations related to deploying JIRA using AWS CloudFormation Templates
  36. Suggestion
    JSWSERVER-25848Change acting user for starting / ending auto-managed Sprint
  37. Suggestion
    JSWSERVER-26506All inline images in Jira notifications should always be clickable
  38. Suggestion
    JSWSERVER-7393Access quick filters via REST API
  39. Suggestion
    JSWSERVER-10762Create a dashboard gadget for the Velocity Chart
  40. Suggestion
    JSWSERVER-15872Rename a Closed Sprint without Re-opening it
  41. Suggestion
    JSWSERVER-16300Swimlane on Kanban Board by Initiative
  42. Suggestion
    JSWSERVER-21353Show only roles that are used in specific project
  43. Suggestion
    JSWSERVER-25122Advanced Roadmaps - Add support for more custom fields to the plan view
  44. Suggestion
    JSWSERVER-25190Allow Advanced Roadmaps to Group by any custom field
  45. Suggestion
    JSWSERVER-26125The "Set Required Field" screen does not take into account mandatory fields from ScriptRunner behaviors
  46. Suggestion
    JSWSERVER-26505Make the Scrum Board Icon different from the Kanban Board in the left menu
  47. Suggestion
    JSWSERVER-26449Linking Jira issues by "the most recently used link."
  48. Suggestion
    JSWSERVER-7265As a user, I want to make estimates visible on cards in Kanban board
  49. Suggestion
    JSWSERVER-10191Please allow to add scripted fields to the issue details view
  50. Suggestion
    JSWSERVER-25077Add Original Story Points field to Portfolio new experience
Refresh results
1 of 3013
Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-25266

JIRA Group as a Team

    • 1
    • 1
    • 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 Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding suggestion.

      People management in JIRA Portfolio would be much easier if we could use JIRA group as a team. We manage groups centrally via LDAP and this way not only importing of Team would be matter of seconds, but the teams in JIRA Portfolio would also always stay up-to-date.
      Thanks for your consideration!

            Aakrity Tibrewal (Inactive) added a comment -

            Dear all,

            I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
            Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.

            Sincerely,
            Aakrity Tibrewal
            Jira DC

            Aakrity Tibrewal (Inactive) added a comment - Dear all, I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged. Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments. Sincerely, Aakrity Tibrewal Jira DC

            Mark J Cunningham added a comment -

            Is there any progress on this, as this would save a lot JML issues and people management

            Mark J Cunningham added a comment - Is there any progress on this, as this would save a lot JML issues and people management

            Lukas Simokaitis added a comment -

            This feature is done in Tempo planning solution. It would be great to have the same in your plugin. In this case Jira groups could be one source of Teams for any plugin solution and a standard way to have a team.

            Lukas Simokaitis added a comment - This feature is done in Tempo planning solution. It would be great to have the same in your plugin. In this case Jira groups could be one source of Teams for any plugin solution and a standard way to have a team.

              Unassigned Unassigned
              594901a20d35 Ondrej Matejka
              Votes:
              29 Vote for this issue
              Watchers:
              19 Start watching this issue

                Created:
                Updated: