• 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.

      Summary

      For applications like Jira and Confluence Cloud, users are able to request apps, which will populate the App requests tab from the administration and trigger an email to admins.

      Suggestion

      Similar to this Jira suggestion and the on-prem edition, this is a suggestion to allow admins to disable users to request it due to reasons like the following ones:

      • Admins might want to use a different tracking/ticket system like Jira to know which apps are the most requested and consider installing/purchasing it.
      • Multiple requests can be sent via email to admins, which could flood the mailbox.

            [MP-194] Ability to disable app requests

            Adding my vote to remove the option for just anyone to request the app through Jira. We have an established onboarding process that also involves legal and cyber review before it even gets to the Jira admins.  This is not the proper method to request an app.  

            Danny Hahn added a comment - Adding my vote to remove the option for just anyone to request the app through Jira. We have an established onboarding process that also involves legal and cyber review before it even gets to the Jira admins.  This is not the proper method to request an app.  

            As with all of the other comments on this topic, the ability for end users to constantly suggest/request add-ons on a "whim" only serves to make it harder to provide a method for making requests like these in any organization that uses products in addition to Atlassian systems.

            Any established organization should have their own method of requesting items like this.

            If the ability to completely remove this functionality isn't feasible, an appropriate alternative would be to replace the option with a displayed message that the admins can modify so instructions can be provided on how to properly submit requests for additional add-ins.

            Anyone posting to this ask is an Atlassian advocate or they would have recommended alternative solutions to their organization. Help us continue to advocate for Atlassian by providing options like this that help our system administrators manage these products.

            Tony Morrison added a comment - As with all of the other comments on this topic, the ability for end users to constantly suggest/request add-ons on a "whim" only serves to make it harder to provide a method for making requests like these in any organization that uses products in addition to Atlassian systems. Any established organization should have their own method of requesting items like this. If the ability to completely remove this functionality isn't feasible, an appropriate alternative would be to replace the option with a displayed message that the admins can modify so instructions can be provided on how to properly submit requests for additional add-ins. Anyone posting to this ask is an Atlassian advocate or they would have recommended alternative solutions to their organization. Help us continue to advocate for Atlassian by providing options like this that help our system administrators manage these products.

            I cannot think of a real world use case where this 'feature' is helpful or useful.

            As detailed in the previous comments, organisations of all sizes have a process for requesting apps that is more sophisticated than ‘I want …’ ‘OK, here you go …’

            And going through all requests and rejecting them with a Message of ‘Rejected, please follow Company procedure’ feels clumsy at best, and leaves the User feeling frustrated and the Admin having wasted time.

            Who does this feature help in its current form?

            If the intention of this feature is to raise awareness of Apps and provide a way for Users to bring them to the attention of Admins, then it needs to fit in with how Organisations work.  For example, adding in the ability to create a Jira ticket in a specific project, with a specific Issue Type / Request Type makes a lot more sense. 

            Adding in the ability to turn off this frustrating ‘feature’ also makes a lot of sense.

            Shona Gilchrist added a comment - I cannot think of a real world use case where this 'feature' is helpful or useful. As detailed in the previous comments, organisations of all sizes have a process for requesting apps that is more sophisticated than ‘I want …’ ‘OK, here you go …’ And going through all requests and rejecting them with a Message of ‘Rejected, please follow Company procedure’ feels clumsy at best, and leaves the User feeling frustrated and the Admin having wasted time. Who does this feature help in its current form? If the intention of this feature is to raise awareness of Apps and provide a way for Users to bring them to the attention of Admins, then it needs to fit in with how Organisations work.  For example, adding in the ability to create a Jira ticket in a specific project, with a specific Issue Type / Request Type makes a lot more sense.  Adding in the ability to turn off this frustrating ‘feature’ also makes a lot of sense.

            This must come. We control the apps to be procured on strict criteria, not the users. If users are interested , they need to raise a ticket and justify - but not a email to admins. We have a designated party who does prechecks for requests and those are not the admins.

            Rather a customisable message to users that stated:

            "You want an app? This is how it works here: Link to a confluence page" for example

            Carsten Schäfer added a comment - This must come. We control the apps to be procured on strict criteria, not the users. If users are interested , they need to raise a ticket and justify - but not a email to admins. We have a designated party who does prechecks for requests and those are not the admins. Rather a customisable message to users that stated: "You want an app? This is how it works here: Link to a confluence page" for example

            Charles Gray added a comment - - edited

            I agree with this feature I don't want users to be able to request apps that are not apart of the bug bounty program and have another admin accidentally approve the app. Also there should be a way in the Cloud to uninstall an app instantly and not have to wait for the 30 day trial to expire this is very annoying.

            Charles Gray added a comment - - edited I agree with this feature I don't want users to be able to request apps that are not apart of the bug bounty program and have another admin accidentally approve the app. Also there should be a way in the Cloud to uninstall an app instantly and not have to wait for the 30 day trial to expire this is very annoying.

            fe11a0bcbbe1 that's unrelated to this particular issue.  I agree, but you may want to find another feature request related to your concern.  i'll mention though that I believe this pricing model follows industry standards.

            Marquita Pruitt added a comment - fe11a0bcbbe1 that's unrelated to this particular issue.  I agree, but you may want to find another feature request related to your concern.  i'll mention though that I believe this pricing model follows industry standards.

            In our case we have 10k users, it is not good for entire site to pay for an addon that only a handful of people will use. the licensing model should be changed to per user that actually edits the data in that add on, or by spaces using it.

            octavian.stanescu added a comment - In our case we have 10k users, it is not good for entire site to pay for an addon that only a handful of people will use. the licensing model should be changed to per user that actually edits the data in that add on, or by spaces using it.

            Aura Hill added a comment -

            This also can be an issue for smaller customers, and it is for my very small organization. I'm a single person handling admin and we have a very limited budget. It takes time to deal with these requests, and politely explain our reason for declining to our external clients who use the site.  It's so easy for them to make the request, but they are not always aware of the potential data or security issues or the cost per users that lead to us declining and are disappointed. It would be much easier to handle if I could turn off requests.

            Aura Hill added a comment - This also can be an issue for smaller customers, and it is for my very small organization. I'm a single person handling admin and we have a very limited budget. It takes time to deal with these requests, and politely explain our reason for declining to our external clients who use the site.  It's so easy for them to make the request, but they are not always aware of the potential data or security issues or the cost per users that lead to us declining and are disappointed. It would be much easier to handle if I could turn off requests.

            We are now an Enterprise customer and, as such, were under the impression this feature could be disabled.  as Marquita Pruitt notes above our users are constantly asking for new apps, but we have our own process for accepting requests for these.  However, because of the Atlassian request option, our users often bypass our process and go through the Atlassian process which is ignored due to the large cost implications and data security concerns mentioned by another user above, along with the additional effort this adds to our admin team.  The current Atlassian approach defeats Atlassian's marketing purposes AND hinders our users from getting the additional support they need.  PLEASE disable this feature.  

            Celeste Freeland added a comment - We are now an Enterprise customer and, as such, were under the impression this feature could be disabled.  as Marquita Pruitt notes above our users are constantly asking for new apps, but we have our own process for accepting requests for these.  However, because of the Atlassian request option, our users often bypass our process and go through the Atlassian process which is ignored due to the large cost implications and data security concerns mentioned by another user above, along with the additional effort this adds to our admin team.  The current Atlassian approach defeats Atlassian's marketing purposes AND hinders our users from getting the additional support they need.  PLEASE disable this feature.  

            Users are constantly asking for new apps, but we have our own process for accepting requests and need to turn this off.

            Marquita Pruitt added a comment - Users are constantly asking for new apps, but we have our own process for accepting requests and need to turn this off.

              Unassigned Unassigned
              gdecampos Giuliano C.
              Votes:
              171 Vote for this issue
              Watchers:
              102 Start watching this issue

                Created:
                Updated: