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

      Issue Summary

      Currently when publishing a forge app a check is made to verify if its being done by the creator and it fails if not. 
      Forge apps can be shared and other users can be given admin right over the app. Forge app admins should be able to publish the forge apps.

      Please change this check to verify admin rights instead of creator.

            [MP-355] Allow Forge app admins to publish apps

            Paul added a comment - - edited

            We, viadee Unternehmensberatung AG (https://marketplace.atlassian.com/vendors/1213394/viadee-unternehmensberatung-ag), vendors of the BPMN Modeler Enterprise (https://marketplace.atlassian.com/apps/1219284/bpmn-modeler-enterprise) support this request.

            In short

            1. Not all people who can publish in the Marketplace should have access to the app owner role in Forge!
            1. Not all app owners in Forge should be able to publish in the Marketplace!

            Explanation

            There can only be one owner of a Forge App and it is the highest permission level a user can have for a given Forge App. This role should be reserved for a management account which is not actually bound to a person. In our case, we have connected it to the Marketplace Vendor account, i.e. our company account.

            Meanwhile, multiple Engineers with elevated responsibility need to have the right to publish versions in the Marketplace, i.e. make changes available to users. 

            Now we have a problem: Multiple people should be able to publish in the Marketplace, but there can only be one app owner. This could be solved with a technical account that the whole team has access to. But we do not actually want all people to have access to the owner account of the Forge App, they should just be able to publish new versions.

            This argument actually also works the other way around: We might have a management account which is owner of the Forge App, but should not publish in the Marketplace as it is only a management account and is not involved in our release processes.

            Paul added a comment - - edited We, viadee Unternehmensberatung AG ( https://marketplace.atlassian.com/vendors/1213394/viadee-unternehmensberatung-ag ), vendors of the BPMN Modeler Enterprise ( https://marketplace.atlassian.com/apps/1219284/bpmn-modeler-enterprise ) support this request. In short Not all people who can publish in the Marketplace should have access to the app owner role in Forge! Not all app owners in Forge should be able to publish in the Marketplace! Explanation There can only be one owner of a Forge App and it is the highest permission level a user can have for a given Forge App. This role should be reserved for a management account which is not actually bound to a person. In our case, we have connected it to the Marketplace Vendor account, i.e. our company account. Meanwhile, multiple Engineers with elevated responsibility need to have the right to publish versions in the Marketplace, i.e. make changes available to users.  Now we have a problem: Multiple people should be able to publish in the Marketplace, but there can only be one app owner. This could be solved with a technical account that the whole team has access to. But we do not actually want all people to have access to the owner account of the Forge App, they should just be able to publish new versions. This argument actually also works the other way around: We might have a management account which is owner of the Forge App, but should not publish in the Marketplace as it is only a management account and is not involved in our release processes.

              b43b2b226e27 Garvita Thakur
              79302268a842 Ana Viseu (Inactive)
              Votes:
              6 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: