Open issues

Order by Priority
  1. Suggestion
    ID-7516Unify user management between Jira/Confluence Cloud and Trello
  2. Suggestion
    ID-7594Implement Out Of Office status for users.
  3. Suggestion
    ID-8321Ability to preset default Roles to "None" when inviting new users (New User Experience)
  4. Suggestion
    ID-8000Extract date when the product access was granted
  5. Suggestion
    ID-8252Set user roles to 'None' by default when inviting a user.
  6. Suggestion
    ID-8809Allow separate allowlist for each API token
  7. Suggestion
    ID-8956Ability to restrict/manage Concurrent Sessions
  8. Suggestion
    ID-8298Remove the "Invite people to Jira" option
  9. Suggestion
    ID-8951Release new API scope for /manage/lifecycle
  10. Suggestion
    ID-8955Provide a clear error message when trying to remove product access from a IDP synced user
  11. Suggestion
    ID-8058Add On Users Should be Removed When the Add On is Removed from the Instance
  12. Suggestion
    ID-8084REST API to provide Recent Devices of user
  13. Suggestion
    ID-8319JIRA Mobile: Report to track the mobile devices and status used to login the JIRA Software by the users
  14. Suggestion
    ID-8346Block group deletion if the group targeted for deletion is used in Jira/Confluence permissions
  15. Suggestion
    ID-8403Update the user status from Invited to Active post signup
  16. Suggestion
    ID-8904Ability to retain the team name when connected to a managed group.
  17. Suggestion
    ID-8953Ability to view JSM licensed users using the "app access" filter
  18. Suggestion
    ID-8954Support for Customizing request endpoint for Microsoft OAuth2 Authentication
  19. Suggestion
    ID-8864Enhance Org-Level Audit Logs to Include Product Addition Activities
  20. Suggestion
    ID-8807Notify users when API key is close to expiration
  21. Suggestion
    ID-6768As an instance admin I would like to invite more than 10 users
  22. Suggestion
    ID-8316Ability to set and get user properties using REST API
  23. Suggestion
    ID-8572Ability of users to be able to remove themselves from the org they aren't managed under
  24. Suggestion
    ID-8774Add Export Users option from Groups menu in Admin Hub
  25. Suggestion
    ID-7711REST API to activate/deactivate users
  26. Suggestion
    ID-7678Provide the ability to change the default session time out for JSM portal-only customer accounts
  27. Suggestion
    ID-8206Historical report (per day) of users taking up a product licence
  28. Suggestion
    ID-7583Add "Manager" as a field for the Atlassian Accounts profile
  29. Suggestion
    ID-7767Allow switching between Public Name and Full Name across Atlassian Apps
  30. Suggestion
    ID-8781API Token Expiry alert notifications for Organization Admins
  31. Suggestion
    ID-7442Have more thorough logs about the API Token usage
  32. Suggestion
    ID-7828As a site-admin, I want to control REST API usage with Application Access
  33. Suggestion
    ID-8351Ability to update "last login" at "Users" when user access by REST API
  34. Suggestion
    ID-8429Approved domain configured with No product access then precedence is given to the product access configuration in "Any Domain"
  35. Suggestion
    ID-8725Add the endpoints used by an API Token
  36. Suggestion
    ID-8902Remove user access via API for Organizations using the Original User management
  37. Suggestion
    ID-8426Allows customized message for users who do not have access to your site/product
  38. Suggestion
    ID-8076Improve annual subscription handling with SCIM user provisioning
  39. Suggestion
    ID-8324User Access Admins should be able to login as another user
  40. Suggestion
    ID-8949Add details about token scopes to the export list of User API tokens.
  41. Suggestion
    ID-8944Allow Admins to bulk handle User Access requests
  42. Suggestion
    ID-8945Allow API key expiration to extend the period
  43. Suggestion
    ID-8946API to Track User Login Frequency in Atlassian Cloud Products
  44. Suggestion
    ID-8948Requesting an API that retrieves directory details.
  45. Suggestion
    ID-8513Admin can set the language preference that overwrites managed users' preference
  46. Suggestion
    ID-8384Allow create user API to select product role(JSM- customer, JSM-agent etc) while creating the user
  47. Suggestion
    ID-7722Ability to include custom information to user profiles
  48. Suggestion
    ID-8707Include the "Last Active date" for Trello Standard and Premium subscriptions
  49. Suggestion
    ID-8942Return 'Invited' status via REST API
  50. Suggestion
    ID-8204Ability to check for and remove email bounces for managed accounts
Refresh results
109 of 586
Uploaded image for project: 'Identity'
  1. Identity
  2. ID-8951

Release new API scope for /manage/lifecycle

    • 2

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      At this moment, the Cloud Admin REST API supports the scopes mentioned in the following link:  

      The scope that grants the necessary permissions to use the Lifecycle endpoints is currently not available. 

      Suggestion

      Release a new scope that provides the permissions to call the endpoints and creates the necessary adjustments in the API key with scopes creation screen.

      Workaround

      To query the Lifecycle endpoints, an API key without scopes can be used. 

            Karin van Driel added a comment -

            It is great to see the more secure definitions for scope on APIs, however the documentation is not very clear. It wasn't for instance clear to me that API scope didn't include all APIs yet, until it was clarified in a help ticket I raised, so there is an opportunity for additional clarity in the documentation and also to link outstanding feature request to the documentation, where they exist. Thank you!

            Karin van Driel added a comment - It is great to see the more secure definitions for scope on APIs, however the documentation is not very clear. It wasn't for instance clear to me that API scope didn't include all APIs yet, until it was clarified in a help ticket I raised, so there is an opportunity for additional clarity in the documentation and also to link outstanding feature request to the documentation, where they exist. Thank you!

              Unassigned Unassigned
              bd4a89fcb3fe Renan Andrade
              Votes:
              2 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: