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

Using JIRA for Scale across a Company

Would like to reach out to find out if there are any companies that have successfully used Atlassian across the firm, to manage cross department initiatives; for example, using Atlassian to manage Sales, Software Development, Client Support, Product Management, Project Management

If there are any, it would be helpful to find out how JIRA projects were set up and structured to achieve this

1 answer

0 votes

Hi @Elliot Braet and welcome to our Community!

I used to work for the company where Jira Software had been initially implemented for our development team but later on we created more projects for other teams as well. We had one for HR where all the stuff-related activity was tracked (hiring/resigning, birthdays, interviews, calendars, etc.). We had a pretty big one for IT with all the inventory, workstations, network information etc. It also had a great change management and we managed to implement a thorough visual access matrix linking employees with instances and assets. Our marketing team also had their own project. All these projects had their respective spaces in Confluence which gave us the opportunity to document processes, create schemes etc. Naturally Confluence and Jira were linked.

That is the magic of Atlassian - it takes your teamwork to the higher level and helps employees to collaborate throughout the company.

Of course, it requires initial configuration, tuning, and specialists with thorough knowledge of the products but the result definitely worth it.

Hi @Grigory Salnikov ! 

Thanks for the quick response! Glad to hear how your previous company used JIRA & Confluence across the company.

Would like to ask if you have any tips or pitfalls to look out for, and how to avoid them? I definitely see with very many moving parts, it is easy for a project/epic to become overly cluttered. On the flipside, if the team is small and often double hat, it may increase the administrative workload to separate each functional role into projects; unless this is one of those a little pain for a lot of reward kind of thing

Would also like to understand more about what you mean by "thorough visual access matrix linking employees with instances and assets"


Like Grigory Salnikov likes this

Thank you for your kind words.

In my opinion, to successfully implement Atlassian products in a company environment one needs to 

  1. Gather information. Involve your team and Cs in discussion about the processes in the company. What are they doing, how they usually do it? Are there repetitive tasks? How the information flows? Are there special business requirements that may affect these processes? Is there compliance your company needs to be in? And last but not the least - what, in their opinion, will help to simplify their work?
  2. Learn the possibilities of the Atlassian products. There should definitely be a specialist (it could be a double hat) with a technical vision into the opportunities the products have to offer. You can become this person yourself if you put enough effort into hitting the books and playing-around with configurations and features. You need someone to show your team what can be achieved with the help of these new tools, how their lives can be easier and to guide them especially at the beginning.
  3. Find the balance between the need and the possibilities. There's never a "perfect solution". You could get easily overwhelmed if you try to cover everything. Thats why it is important to
  4. Start with the basics. Take most frequent tasks and most important processes and try to implement them. After that you could "build-on" gradually expanding and adding more details and advanced features. It would be easier and transparent for everyone.
  5. Be patient. Great things grow with time and usually from humble ones :) In our environment we would always add new things and features, change something, cover some new process, etc. It was really an ongoing process but after approximately half a year we all were happy to have handy tools and enjoyed our work even more.

Don't forget about the Atlassian Marketplace - it is a wonderful place to get awesome apps. Almost half of the wow-features in our environment we got from different add-ons (free or paid). Though some of them could be tricky and require additional effort to implement up to some kind of programming skills.

By the way, the notorious "thorough visual access matrix linking employees with instances and assets" was based on the following app:

Links Hierarchy for Epic & Portfolio

We had one project for all the employees and another one for all the IT systems and assets (workstations, servers, corporate accounts, resources, even services). We created a number of bidirectional links ("has access to"/"has user", "is hosted on"/"hosts", "is an admin on"/"has admin"...) and intertwined all our entities. That was hard work indeed but the result was awesome. We adjusted our processes in a way that every change, for example when an employee is granted access somewhere, would be reflected in our access matrix. This way when a person is hired depending on his or her role she's granted certain permissions and they are become visible in the matrix. When a person leaves this matrix didn't let us forget to remove their access. Or we could also just click on some server or system and get the comprehensive information about who was the administrator, which user accounts were present in the system etc. along with all the necessary technical IT information.

After a couple of years I started to see that we are limited only by our imagination and almost every wish could be granted inside a single-vendor environment.

This Community has also played a great role. It is a good place to get answers and share your experience. Usually when I'm stuck in a dead-end someone here always manages to help me.

I wish you the same. 

Have a nice day!

That's a really interesting and detailed response!  Thanks for sharing.

I'm curious how you managed the 'people' element?

Most project managers I speak to really struggle to get anyone other than the tech/project team engaged in Jira.

Like Grigory Salnikov likes this

Hi @Ben Munk ! Thank you.

I agree that this is the trickiest element here. People are inert and usually stick to something they're accustomed to. The thing that worked well is showing how their work can be improved through organising, visualisation, and wow-features. And not only their work as a single worker but rather as a team. We always tried to present just the result - the final process or feature, usually hiding how hard it could be for us to deliver them from technical or configurational point of view.

You know, after a while when people understood and accepted all the advantages they started to be proactive and suggested some improvements themselves. That was the feedback we were hoping for. This can only happen when one first sees how the system works, he then starts to ask "what about that?", "can we do this?", "will this work?" and more often with Atlassian products the answer is "yes".

To tell the truth, sometimes it requires superiors to "push" their workers a little towards using these new things but in the end everyone is happy. 

I see how one can easily overload the processes and scare the employees away with all the unnecessary details or moves. Thats why it's important to first hear the needs, gather information, and only after that offer a balanced solution.

Summarising it all: gather information, hear your coworkers, get them involved, demonstrate the advantages, don't overload.

Like Ben Munk likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events