One easy tip to avoid nuking production in Atlassian Jira and Confluence
In our previous post we discuss some automated steps you can take to help get your staging environment set up correctly. But once you’re there, new risks come up. In this blog, we focus on what you can do in both your production and staging environments to ensure your admins are less likely to confuse the two and break something.
Did you ever delete a scheme and then freak out when you realize you did it on the wrong system? When you’re heads down trying to get things done, it’s easy to lose track of which system you are on.
We’re no different, and have been guilty of this in the past. To help reduce the risk of this kind of mistake we came up with a simple visual cue to help.
A light red tint* is applied to all pages when viewed by an admin user, reminding them that they are on a production instance. When they switch to staging, we do the same with a light green* tint. Keep in mind that while this article talks about Jira, the same code can be adopted (with a bit of tweaking) to Confluence or any other Atlassian tool that allows you to inject your own code. How did we accomplish this? With a little bit of JS and CSS in each systems announcement banner:
* We understand that this does not work for individuals who are colorblind. If you have any feedback on similar techniques that work just as well for colorblind individuals please share them with us in the comments.
Planning projects at a team’s level is quite the journey. Thankfully, Jira is built to streamline the process and help thousands of teams with their project planning. Today we will look at the add-on Tempo Planner, which helps teams take project planning in Jira to the next level.
Maybe you’ve been in this situation: one department is using monday.com, and another department is using Jira. It doesn’t have to halt productivity.
Is your marketing team drowning in projects? Here’s how we use monday.com to manage marketing projects.