When designing Jira Service Desk implementation for your organization, there are tons of choices that need to be made. One important decision during this process is determining how to break down your service desk - Will you have one Service Desk for all of the teams working in the organization? Or will you build out multiple service desks and use the Help Center to route users to different Portals?
2 min read
Teams new to Scrum face lots of decisions - one key decision for teams to perform efficiently is determining sprint length.
2 min read
Using Atlassian tools for your DevOps endeavor sets your teams up for success. While there are many challenges in a new DevOps implementation, the tools you use don't have to be one. A quick search will show you that there are many ways to fail at DevOps - it requires massive organizational change and lots of moving pieces to function, so getting started can be tough. It might be a painful process to initiate, but as we've seen, it's absolutely worth it. With that in mind, while you focus on the big questions (Like how in the world can I deploy daily/weekly/hourly?), the Atlassian stack helps you out in some ways you may not have even considered. With one (or all) of these questions out of the way, you can get back to focusing on what matters: the people and processes that you're revolutionizing.
7 min read
This resource is for you if you've read Atlassian's documentation but are still confused on how to import linked issues.
4 min read
One of the most powerful integrations in the Atlassian ecosystem is the native link between Jira and Confluence. For users working in both tools, the transition can be seamless if you do it right, but clunky if you don't.
Now, what if I told you there was just one Confluence macro you could start using today that will immediately make reporting in Confluence easier and help you (and your team) keep track of your work? The Jira Issues macro is the go-to when reporting in Confluence.
Here are some tips to get your team to live their Atlassian life-to-the-fullest.
4 min read
While creating a space for your team in Confluence may seem like a simple undertaking, creating one that users actually want to interact is far from easy. We know what can happen when you miss the mark: you've got a team space, but it's a mess - nobody knows where to find anything, there's no consistent structure, and nobody actually uses it. It’s not hard for a space to become a documentation black hole - documents enter, never to be seen again.