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

      For the Standard Plan to say it offers Service Management then there should be the capability of at least 1 sandbox for a chargeable instance.

      I would ask that Atlassian review their policy on this urgently.

      Free - No Sandbox

      Standard - 1 sandbox per instance
      Option for additional sandboxes at a price  (rolling monthly with Opt out any time per sandbox) 

      Premium - Unlimited sandboxes.
      or 10 sandboxes with option of additional sandboxes and a price (rolling monthly with Opt out any time per sandbox) 

      • Benefits:
        • can you safely develop and test new features properly.
        • Allows for larger Options testing for Projects
        • Multiple diverse Projects being tested at the same time
        • More Profit for Atlassian !!!
        • Scalability for Admins
        • Less risk to deployment of new features in the Service management too for standard tier users
        • Actual service management function in the standard tier !!

      Matt

          Form Name

            [COMMERCE-77] Standard Plan Sandbox - and scalable add on feature.

            We're on JSM Premium, have different staff working on different elements of a major reconfiguration, and having only one sandbox per product is severely impacting our ability to experiment with improvements.

            Even if we were still limited to being granted one sandbox per product but had the ability to assign those sandboxes among our licensed products, it would be a significant improvement. For example, we use Jira, JSM, and Confluence but currently don't use our sandbox entitlement for Jira or Confluence. It would be beneficial to us if we could instead have 3 JSM sandboxes.

            I agree that Standard customers should also get at least one sandbox environment.

            Matt.Zwager added a comment - We're on JSM Premium, have different staff working on different elements of a major reconfiguration, and having only one sandbox per product is severely impacting our ability to experiment with improvements. Even if we were still limited to being granted one sandbox per product but had the ability to assign those sandboxes among our licensed products, it would be a significant improvement. For example, we use Jira, JSM, and Confluence but currently don't use our sandbox entitlement for Jira or Confluence. It would be beneficial to us if we could instead have 3 JSM sandboxes. I agree that Standard customers should also get at least one sandbox environment.

            Matt Smith added a comment -

            The Irony is that Dev/Prod is a Quality management item and ITSM (ITiL) best Practice....

            Yet Atlassian have not adhered to the best practice requirements of their customers !!

            Should not even be in a state of gathering interest it should be in Atlassians must do's.

            Matt

            Matt Smith added a comment - The Irony is that Dev/Prod is a Quality management item and ITSM (ITiL) best Practice.... Yet Atlassian have not adhered to the best practice requirements of their customers !! Should not even be in a state of gathering interest it should be in Atlassians must do's. Matt

            This is something that should already have been an option. Simply because a customer is on Standard does not mean that we shouldn't be entitled to a DEV/PROD setup. This is actually a major downside of using the Atlassian suite.

            Robert Robinson added a comment - This is something that should already have been an option. Simply because a customer is on Standard does not mean that we shouldn't be entitled to a DEV/PROD setup. This is actually a major downside of using the Atlassian suite.

            Susan Waldrip added a comment - - edited

            Thanks for opening this issue, Matt! Having a safe, straight-forward way to move changes into Prod from a Dev or Test environment AND be able to safely and quickly roll them back if needed is critical for Standard Plan subscribers.

            Susan Waldrip added a comment - - edited Thanks for opening this issue, Matt! Having a safe, straight-forward way to move changes into Prod from a Dev or Test environment AND be able to safely and quickly roll them back if needed is critical for Standard Plan subscribers.

              Unassigned Unassigned
              96d36421191f Matt Smith
              Votes:
              10 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated: