Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Avoid ripping out your hair with Easy Power Scripts management + Configuration Manager

There you are, leaning back in your chair satisfied with the changes you've made. 

  • The Power Scripts SIL® scripts are done and behaving the way they should. Beautiful.

  • The workflows and custom fields have been adjusted to meet the requirements. Perfection.

Time to test...because you know, you need to see these changes in action outside of your development instance.


While you may have only 2-3 scripts to move, you have to set the CRON jobs and listeners and schedulers and...sigh… 

And now you have to configure the workflows and statuses. Then you move onto the custom fields and set those to the right screen. Okay, now that you have everything into the test instance, it's time to wait for the team to do their validation. After you get the green light to deploy to production, you have to once again move the SIL® scripts and configure the prod instance accordingly.

Six months later, you get a notice that the company is going to migrate Jira to a new server and new database (WHY!?). Time to do this all over again...*Weeps with full-blown sadness

A few weeks later, someone accidentally blows up Jira and all the data gets deleted. At this point, you're pulling your hair out in complete frustration. 6 months of work down the drain and you have to yet again redo all the configurations once the new Jira instance is stood up. But wait. There’s more. But you’ll also have to rewrite the SIL® scripts plus the smaller code modifications added over time.

Angry Computer GIF


Botron's Configuration Manager can simplify this entire process! Since Power Scripts for Jira is now fully integrated with Configuration Manager, SIL® scripts will be included in any snapshots you take when you migrate changes and/or entire instances. What would have taken hours or days to complete can now be done in a few clicks! *Weeps with joy

Screen Shot 2020-08-10 at 1.47.34 PM.png

You may be thinking that you're safe from data wipes by taking regular Jira backups. However, you may not be aware that the add-on settings/data are not stored in those backups. However, Configuration Manager does store them. Which means you'll be able to roll back to a previous version and the scripts themselves will be restored!

Check out Botron's Configuration Manager and Cprime's Power Scripts for Jira.



Log in or Sign up to comment
AUG Leaders

Atlassian Community Events