You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I manage a team of business system analysts, developers and administrators.
We manage six different major systems as well as numerous smaller add-on tools.
Each system has one to two primary admins that do not work in the other systems.
There are a couple analysts who span across all of the systems and projects though.
I'm pretty new to Jira and have been tasked with setting up a project or set of projects that will track my teams work in a single reportable way to measure everyones workload.
With the different stakeholders and users, I think that we will need multiple simultaneous sprints.
For instance, I have an entire backlog for Salesforce (Service & Sales), Netsuite & OpenAir, HRIS, and Sharepoint, as well as BI/Analytics which spans all systems.
Each of these backlogs has major projects, bug fixes, and smaller requests that need to be prioritized individually, but reported on as a singular team.
We are working in an Agile manner.
What would the community recommend as the best way to set up a singular or multiple projects to best capture these activities and requests, and how should I utilize epics/stories/tasks to categorize everything that comes in across all departments from the company?