Log inSkip to main contentSkip to sidebar
Something went wrong, please try again.
Create and track feature requests for Atlassian products.
  • More
    DashboardsProjectsIssues
  • Give feedback to Atlassian
  • Help
    • Jira Core help
    • Keyboard Shortcuts
    • About Jira
    • Jira Credits
  • Log In
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

Open issues

  • All issues
  • Open issues
  • Done issues
  • Viewed recently
  • Created recently
  • Resolved recently
  • Updated recently
View all issues and filters
Order by Priority
  1. Suggestion
    MP-372Allow Active Installation Filtering by Hosting Type
  2. Suggestion
    MP-371To show Manual invoice flag in transactions API
  3. Suggestion
    MP-350Add a field to identify Cloud/DC licenses related via dual licensing
  4. Suggestion
    MP-74Show user responsible for action on Add-on Audit Log
  5. Suggestion
    MP-345Need information about open quotes for a given license/customer
  6. Suggestion
    MP-278It should be possible to edit the profile of the Atlassian Account of the users created for marketplace apps
  7. Suggestion
    MP-369Include Account Owner Email in Marketplace APIs or Partner Reports
  8. Suggestion
    MP-185Enable the "Uninstall" button no matter if it's under subscription or not
  9. Suggestion
    MP-368Allow admins to limit add-on access to specific projects in Jira
  10. Suggestion
    MP-367Partner discount amount data rounding off in Get Transaction API
  11. Suggestion
    MP-194Ability to disable app requests
  12. Suggestion
    MP-88Separate license base for Addons / Allow admin to limit add-on licenses to specific users
  13. Suggestion
    MP-365Allow EU as a Data Residency value
  14. Suggestion
    MP-255Forge App compatibility with Bitbucket for marketplace
  15. Suggestion
    MP-363REST API to return the count of reviews of the app
  16. Suggestion
    MP-360Add app "Access Token" support for Forge apps
  17. Suggestion
    MP-289Allow partners to transfer apps across partner accounts themselves (self-serve)
  18. Suggestion
    MP-357Enhanced License Record Visibility for Marketplace Partners
  19. Suggestion
    MP-351Filters on License Report should have same functionality in all cases
  20. Suggestion
    MP-355Allow Forge app admins to publish apps
  21. Suggestion
    MP-100Add the possibility to remove popular add-ons section from the Apps menu and add a scroll bar to show more installed apps
  22. Suggestion
    MP-354To be able to write release notes if a new version is automatically released
  23. Suggestion
    MP-347Discount_array amounts should follow same logic as the amounts on the rest of the Transaction
  24. Suggestion
    MP-349Add a notification in the UPM to redirect customers where to unsubscribe or uninstall apps
  25. Suggestion
    MP-343Provide sales type for manual transactions
  26. Suggestion
    MP-336Align Sandbox maintenanceEndDate filed with Production
  27. Suggestion
    MP-330Request for Re-evaluation of Version Visibility Approach on Version History Page
  28. Suggestion
    MP-333Adding the promo code details in the Reporting API for Manual discount types also
  29. Suggestion
    MP-202Unable to edit the installation instructions for App listed on Marketplace
  30. Suggestion
    MP-322Apps should have option to receive updates manually or automatically
  31. Suggestion
    MP-314Ability to view disabled addons in the Central user management
  32. Suggestion
    MP-309Updating Vendor Profile with Diacritic Characters Causes Error
  33. Suggestion
    MP-308Youtube end cards not displaying in embedded videos on Atlassian Marketplace
  34. Suggestion
    MP-238Create requirement to have Google Ads Conversion Tags set up on the landing pages
  35. Suggestion
    MP-301Ability to Restrict Users from Requesting Add-ons Directly from the Marketplace
  36. Suggestion
    MP-300Having a flat pricing model for cloud apps for tiers above 10 users
  37. Suggestion
    MP-84Include Add-ons changes information in Audit Log i.e. install / enable / disable apps in marketplace
  38. Suggestion
    MP-86Allow marketplace product licenses to limit the number of users they apply to.
  39. Suggestion
    MP-293Unable to Install App "Apptio Cloudability" in Jira Instances (EU Region)
  40. Suggestion
    MP-297Improve the utility of the ACCOUNT_ID
  41. Suggestion
    MP-276Trial App subscription cancellation
  42. Suggestion
    MP-291Enhancement Request for PDF Download and Page Persistence in Pricing Calculator
  43. Suggestion
    MP-290Marketplace App shown across products in calculator
  44. Suggestion
    MP-292Atlassian Troubleshooting and Support Tools compatibility with 9.1 DC
  45. Suggestion
    MP-75Add ability to remove add-on / plugin / app data as well upon Uninstallation.
  46. Suggestion
    MP-71Restrict the ability to add apps for Administrator only
  47. Suggestion
    MP-228Preserve previous version information listings on Marketplace
  48. Suggestion
    MP-285Add a label or badge for beta apps on marketplace
  49. Suggestion
    MP-280When an app requires a manual update, notify the user so they can start the update and avoid potential issues.
  50. Suggestion
    MP-77Support mentions in MS Teams integration
Refresh results
1 2 3 4 5Next >>
1 of 201
Uploaded image for project: 'Atlassian Marketplace'
  1. Atlassian Marketplace
  2. MP-372

Allow Active Installation Filtering by Hosting Type

Log In
Gathering Interest
Export
undefinedView workflow
XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • Partner - Experience (Publishing, Reports, Account)
      • ecohelp
    • 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.

      Suggestion

      Currently, the active installations tab only allows filtering by version, which makes it difficult to distinguish between Cloud and Data Center installations. Please add a filtering option by hosting type to make it easier to manage and analyze installations across different platforms.

      The reason is, currently, version numbers for Data Center apps are assigned manually, while Cloud app versions are generated automatically. In the past, when the app was Connect-only, Cloud versions included an “-AC” suffix, making them easy to differentiate. However, since migrating to Connect-on-Forge, Forge-generated version numbers no longer include any markers to distinguish them from Data Center versions.

      This creates confusion in the active installations tab, where the same version number (e.g., 2.2.0) can appear for both Cloud and Data Center, making it unclear which version belongs to which hosting type.

      To resolve this, please introduce a way to filter or clearly distinguish active installations by hosting type. Ideally, this could include separate “App version” charts for Cloud and Data Center, as comparing these versions directly is uncommon. Alternatively, adding a marker or label to specify the hosting type for each version would also address the issue.

            • All
            • Comments
            • Work Log
            • History
            • Activity
            There are no comments yet on this issue.

              Unassigned Unassigned
              a60056aed681 Rosa Faghihi
              Votes:
              6 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Yesterday 3:54 AM
                Updated:
                Yesterday 4:21 AM
                • Atlassian Jira Project Management Software
                • About Jira
                • Report a problem
                • Privacy policy
                • Notice at Collection

                Atlassian