Open issues

Order by Priority
  1. Suggestion
    JSDSERVER-15538Improve Object Type Selection When Moving Objects in Jira Assets
  2. Suggestion
    JSDSERVER-15060Increase limit for object type searches during object creation
  3. Suggestion
    JSDSERVER-8647Allow configuration of the "Jira Administrator" permission scheme to remove access to Insight Object Schemas
  4. Suggestion
    JSDSERVER-15625Customer wants to keep a global timezone in Jira for old and new issues.
  5. Suggestion
    JSDSERVER-78Ability to view Elapsed Time as a column in Issue Navigator or in Export
  6. Suggestion
    JSDSERVER-513Make it possible to use service desk in combination with subdomains
  7. Suggestion
    JSDSERVER-614Allow users to edit their own comments
  8. Suggestion
    JSDSERVER-818JSM should send reply or notification when mail handler cannot create or update issue
  9. Suggestion
    JSDSERVER-1015Active Directory integration for customers
  10. Suggestion
    JSDSERVER-1637As an SD Admin, I want the ability to customize the Public Sign-up Form / Page
  11. Suggestion
    JSDSERVER-4102As a Service Desk Customer, I'd like the ability to "raise this request on behalf of" other customers
  12. Suggestion
    JSDSERVER-4636View linked issue in the Customer Portal
  13. Suggestion
    JSDSERVER-4650Add an "is empty" operator on the JSD "SLA" field type.
  14. Suggestion
    JSDSERVER-4698Provide an outgoing email logs
  15. Suggestion
    JSDSERVER-4922Allow JSM to make comment required on transition in Customer Portal
  16. Suggestion
    JSDSERVER-5812Add custom fields to variables list in Canned Responses
  17. Suggestion
    JSDSERVER-7540Not able to Restrict "Bulk Action" permissions
  18. Suggestion
    JSDSERVER-8054Export Issue to PDF - attributes
  19. Suggestion
    JSDSERVER-8540IQL for object.history
  20. Suggestion
    JSDSERVER-11013Provide a way to export complete Insight Object schema data
  21. Suggestion
    JSDSERVER-13052Add support for using a placeholder for custom field of request type in Assets custom field's filter issue scope on customer portal
  22. Suggestion
    JSDSERVER-13983Permission documentation for Recalculate all SLAs feature for an issue
  23. Suggestion
    JSDSERVER-93Allow editing of fields / details through the service project request (post-creation)
  24. Suggestion
    JSDSERVER-222Jira Service Management Reports gadget for Jira Dashboard or Confluence page for agents
  25. Suggestion
    JSDSERVER-328Allow Assignee to be Shown on Customer Portal
  26. Suggestion
    JSDSERVER-365Service Desk Gadgets for Customers
  27. Suggestion
    JSDSERVER-1317Ability to copy request types to another Service Desk.
  28. Suggestion
    JSDSERVER-4452Add a possibility to hide error message
  29. Suggestion
    JSDSERVER-4535Customise SLA Colors
  30. Suggestion
    JSDSERVER-5397Restart JIRA mail services manually
  31. Suggestion
    JSDSERVER-5552As an admin, I would like to restrict agents/admins from creating new customers
  32. Suggestion
    JSDSERVER-6735Request shared with an organization should allow customers to share the request with themselves
  33. Suggestion
    JSDSERVER-7569Revert Changes
  34. Suggestion
    JSDSERVER-7623REST API - add Append param when using PUT to update an Object's Attribute
  35. Suggestion
    JSDSERVER-7722Clone feature - Attachment option
  36. Suggestion
    JSDSERVER-8706Create a cleanup mechanism to Assets Object History
  37. Suggestion
    JSDSERVER-11187Ability to Persist Value of User Type Attribute (owner of an asset) in Insight
  38. Suggestion
    JSDSERVER-13977Ability to create Kanban Board for Service Management
  39. Suggestion
    JSDSERVER-366Ability to show/hide Queues with specific users/groups
  40. Suggestion
    JSDSERVER-1012Possibility to hide/disable the customer portal and help center
  41. Suggestion
    JSDSERVER-1627Create ability to customize the Customer Portal URL in Jira ServiceDesk
  42. Suggestion
    JSDSERVER-2415Consider making possible to view JIRA Core reports in a Service Desk project type
  43. Suggestion
    JSDSERVER-3308Ability to hide agent name in customer portal
  44. Suggestion
    JSDSERVER-3948Allow Request Participants role / group to be added to Issue Security Schemes and Project Permissions
  45. Suggestion
    JSDSERVER-4328Add fields (view only) in Customer Portal
  46. Suggestion
    JSDSERVER-4648Allow the hiding of the "Share with" option from the customer portal
  47. Suggestion
    JSDSERVER-4890Option to set permission for Agent to create customer
  48. Suggestion
    JSDSERVER-5463Prevent Service Desk Agents from Creating New Customers from the Project Page
  49. Suggestion
    JSDSERVER-7142Ability for other text/multi-text custom field to have a wiki style renderer in JSM Customer Portal
  50. Suggestion
    JSDSERVER-7160Import feature - "Do not create new objects"
Refresh results
1 of 3914
Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-15538

Improve Object Type Selection When Moving Objects in Jira Assets

    • 1
    • We collect Jira Service Desk 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.

      When moving objects from one Object Type to another within Jira Assets, the dropdown menu used to select the target Object Type is currently limited to displaying 1,000 entries. This limitation is due to the hardcoded limit in the API endpoint:

      Endpoint: assets/objecttypes/picker/create?schema=1&limit=1000

      If the number of Object Types exceeds 1,000, some Object Types may not be visible in the dropdown, making it difficult for users to select the appropriate target.

      Workaround

      One temporary workaround is to manually modify the limit in the API request using the browser's developer tools to increase the number of entries shown. However, this solution is not practical or feasible for all users, especially those without technical expertise.

            Oleksandr Russu added a comment -

            Corresponding request PSSRV-133835 has been resolved as Atlassian Bug.

            Oleksandr Russu added a comment - Corresponding request  PSSRV-133835 has been resolved as Atlassian Bug .

            Oleksandr Russu added a comment -

            Hello 072fabfd41a3,

            Could you please clarify why this issue has been classified as a suggestion rather than a bug?

            Thank you,

            Oleksandr

             

            Oleksandr Russu added a comment - Hello 072fabfd41a3 , Could you please clarify why this issue has been classified as a suggestion rather than a bug? Thank you, Oleksandr  

            Oleksandr Russu added a comment -

            Hello,

            Is there any update or estimated timeline regarding this issue? It’s currently blocking several processes related to moving objects between types and is causing cascading issues.

            Best regards,

            Oleksandr

             

            Oleksandr Russu added a comment - Hello, Is there any update or estimated timeline regarding this issue? It’s currently blocking several processes related to moving objects between types and is causing cascading issues. Best regards, Oleksandr  

            Oleksandr Russu added a comment -

            It should be not an improvement, but a fix for the issue when users are not able to move objects between types from UI, if schema has more than 1000 object types.

            Oleksandr Russu added a comment - It should be not an improvement, but a fix for the issue when users are not able to move objects between types from UI, if schema has more than 1000 object types.

              Unassigned Unassigned
              072fabfd41a3 Shreekesh Mohan
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: