Adithya Ramesh Atlassian Team

Hey Mia! Absolutely. Spotting changes early and knowing who owns the follow-up are essential to making change manageable.

Great point, Maria! Making sure the system continues to deliver its intended outcomes is a shared responsibility. We encourage admins to check in regularly with end users and maintain a clear feedback channel to understand which changes are working well and which need attention.

Thanks, @Julia Foden. I appreciate the candid feedback. We’re working to improve both visibility into upcoming changes and your control over when they reach production. One capability we’re developing is Change Pipelines. This will let you see significant Atlassian-initiated changes in your sandbox, test them, and…

Thanks, Anahit! Would love to hear which part of your approach has worked best for your team.

Thanks, @Viswanathan Ramachandran! I love your emphasis on measuring the success of a change by the business outcomes it delivers.

Hi @Kim-Stacey Kidder! Yes, this is currently still in public Beta, and we are working towards general availability. I'd absolutely love to hear feedback, you can either share it with me via email at aramesh@atlassian.com, or if you have questions and feedback, you can directly setup time with me to chat about it live…

Hi @John Mustac ! Yes, absolutely - the capability can be used to move config changes both from one sandbox to another, as well as from a sandbox to its associated production environment.

Thanks @S Fong - Since it is a public beta, it should already be available on your instance. Happy to help you get started with using the capability! 

Hi @Suresh , it is currently a part of our backlog to explore how we can enable marketplace apps to also leverage the capability and deploy their config alongside Jira configs. Please do watch this ticket for updates, and vote for it - this would help us prioritize this enhancement. Thank you! 

Thanks for the feedback Sami. I definitely agree that it'd help to have these marketplace app related shortcomings surfaced before the deployment is undertaken so that you can take informed decisions based on that. I created this ticket to track this suggestion - would be great if you could please add your experience in…

Hey @Rachit Singhal ! One of the prerequisites to using the capability is to have performed a "Copy All projects" from your production to your sandbox before the cutoff dates (available here). If this has been done, we would be able to identify when a particular config is updated - even if you change it's name or…

Hey @Sami Shaik ! Thank you for the amazing write-up, and for the great feedback around the capability! We are actively making improvements around some of the areas you called out - you should see a noticeable improvement in the time taken for the scan and validation over the next few months (and fixes to some of the…

Hi @Mariusz Krajewski ! Unfortunately, we do not have timelines for when this capability would be available for JPD. However, it'd be great if you could vote for, and watch this Jira ticket - this would help us prioritise this on our roadmap. Thanks! 

Hi @Sean Meenaghan ! The change will automatically land in your production sometime before the end of the month. However, if you want to, you can manually trigger the change by navigating to <sitename>/jira/settings/issues/field-configuration/enable-field-scheme Where you'll see a button to kick-start the process. Hope…

Hi @Benjamin Zhou ! This is happening because Jira is transitioning to New Field Schemes - More on that here: https://community.atlassian.com/forums/Jira-Cloud-Admins-articles/Announcing-General-Availability-of-Field-Schemes/ba-p/3246894 This progressive rollout of the new Field Schemes has already reached your sandbox,…

Hi @Wade Hephner ! We had a temporary issue in our sandbox systems which would have caused this issue. The issue is now resolved - could you please try it out again? Please feel free to reach out to our support if you run into further issues. 

Hey @Kent G 👋 We're still gradually rolling this out. Since it's a brand-new capability, we're taking a slightly longer rollout approach so we can catch and fix any bugs before making it available more broadly. That said, if you need access sooner, just send me an email at aramesh@atlassian.com with your Organisation ID,…

Thanks for the detailed response @Ignacio Pulgar - Appreciate you taking out the time to explain this to me. Though I don't have an immediate answer, I will surface this to our teams internally and keep this Jira ticket updated with progress. I'd urge you to vote on the ticket to help us prioritise it, and watch the ticket…

Hi @Gabriel Roth ! We are actively rolling this change out now - we are hoping to make it available to all customers by the end of next week.

Thanks @Jason Krewson ! Excited to see you try this soon!

Thanks @Arkadiusz Wroblewski ! Would love to hear your experience after you start using this!

Hi @Ignacio Pulgar Thanks for the feedback, and great question. You're right that sandboxes aren't covered by the same SLAs as production, but I'd love to understand your concern a bit better so we can help.Generally, when we hear from customers about this, the concern is around performance. From a functional perspective,…

Thanks @Roksolana SLiusar ! We are working on improving the performance for copying from prod to sandbox, but I'd love to know if there's any specific improvement that you'd like to see.

Hey @Vijay Khairnar ! I am Adithya, the PM for Sandboxes. Unfortunately, it is an existing limitation today, where all configurations are copied even if you choose to copy a single project. The only workaround is to create a new sandbox for that project, or perform a "Copy all projects" into your sandbox, which will…

Hey @Juan Diaz Davila - I am not able to find your request on Feb 19, could you shoot an email to aramesh@atlassian.com with your ticket number or your org ID and we can take it from there. Thanks!

Hi @Juan Diaz Davila ! You should have received an email from our automated system if it had been enabled for you. Can you please shoot me an email to aramesh@atlassian.com with either your ticket number or your email id? I can check and confirm your status. Thanks!

Hi @Juan Diaz Davila ! Currently we have a long backlog of customers, you can expect a response from us as soon as we are able to onboard more customers (this might take somewhere between 2-4 weeks)

Thanks @Danno Would definitely appreciate any additional feedback you might have. Shoot me a mail to aramesh@atlassian.com, and I will work with you to find time.

Hi @Henry ! I am Adithya, the Product Manager for Sandboxes at Atlassian. We are currently working on a solution to improve this experience of deploying tested configuration. I'd urge you to check out this tool that is currently available in closed beta to see if this solves for your use cases. There is a form attached to…

Hi @AJ McBride ! In our first cohort of rollout, we are targeting Enterprise customers, since they have multiple sandboxes that will allow them to test the feature between two sandboxes, before using it on the production. We will keep you posted as we progress, and will update the community post when we roll out the…