Hi, i`ve been using jira for about 5 years for the development team.
In my company, we also have more areas (design, support, marketing, technicians)
They don`t use jira, but we wan`t to implement it cross area, because sometimes projects are cross area, and also to registered it, not just in the email.
The original idea is to create a main project with the board, and then one project with a board for each area.
Then, we should add an epic into the main project, and then create tasks on the specific project, associated to the epic.
Doing that, the PM or a PL could see all projects (epics) opened into the main project, and the tasks associated into the affected boards.
Is it a good way to implement it? Do you recommend me another way to do that?
I think this is a good approach. In fact I've built for several companies in a similar way:
The variations I have are:
PS: I started Dragonboat to compliment Jira capabilities as outlined above.
That could work but could also become very convoluted as you add additional projects and tasks. I am a PM and me and my team are responsible for running hundreds of projects at times. I would have issues keeping track of everything if I configured it that way.
I would suggest looking at additional products or apps that can provide insight at a higher level over everything that is happening:
These are a couple I have used that could help you with what you are trying to do.
When starting out it is more important to have solid processes, procedures and continuity across projects so your PM can more easily monitor and control them.
Jira dashboards and reports can be a great place to start and then you can get more complex from there.
We are probably one of the heaviest users of integrated teams using Jira for our product teams for content and knowledge work. These teams (30-40) consist of Marketers, Designers, Developers, Team Leads for Approvals, QA Specialists, Copy Writers, Copy Editors, etc.
We use a single, albeit large, workflow that moves through the various activities (statuses/steps in the workflow) for the teams. We use "flexible" transitions/statuses so each team can decide whether each activity is needed or not for a particular issue (for example, does an email need visual design or not).
Each product team is a separate Jira project, but they might have multiple boards. At the very least each team has a Master Board that has all possible activities/statuses on the board, grouped in related columns (for example, Create column includes Write Copy, Visual Design, Copyediting, etc.). The next column would handle approvals and revisions (reworks).
So each project is attached to the same shared workflow scheme, permission scheme, issue type scheme, screen scheme, etc. to provide commonality and reduce maintenance. It's complicated but works great for us. :-)
We also use Epics within each Project but also Epics that might span the entire organization (950 team members). For example, the annual Christmas Marketing Campaign might affect multiple websites, products, eCommerce, etc.
That's a high level overview but I hope it helps a little.
Hi @Matias Silversteyn - did any of these answer your question for you? Is there anything else we can help guide you with? If not, can you click on the Accept answer button for those that provided the answer for you so we can close this one out? Thanks!
When to use CSV importer When managing your processes in Jira, there are many occasions where you need to create a lot of tasks. Creating them one by one will cost you a lot of time and effort and i...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event