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

Best suggestion to set up methodology

Greetings Brains Trust,

Our team are currently documenting the design requirements for how we will be using Jira Core for our business team task management and I was wanting to get some suggestions or feedback on the best way to structure our config?


We're a business improvement team that is also responsible for the Document QA system. We have BAU tasks such as document reviews and updates and well as GRC tasks for the department and managing the staff encouragement program.. On top of this we also have a large portion in working on business and process improvement projects/initiatives. We need to be able to report on the following;

  • Details or tasks outstanding/inflight.
  • Visibility on current and upcoming workload (based on estimates/sizes etc) for each team member
  • Time of flight
  • # of high level Requests from each area. (identified through a custom field)
  • Number of lower level tasks (identified through a custom field)

My main question is, based on the reporting we require, which of the following hierarchies would you suggest? 

Option 1) Each top level area, is a separate project, with the Epics as the next level of reporting for each task? (this would entail custom reports which we don't have expert support to create)


Option 2) Having just one Project for the whole team, and then using Epics as the top level of task subject with each request being a task with it's sub-tasks?


Any suggestions or insight into what others have done would be greatly appreciated.


1 answer

0 votes
Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 25, 2020

Hello @Dave W

Welcome to the Atlassian Community!

Taking a look at all the 5 features you would like to implement to achieve your goals, I believe that a Classic business project would be enough, supposing the "Time of flight" will also be added as a custom field.

About the hierarchy options you'll be using, the best way to determine the best approach would be by defining how you would like to report your results and progress on those issues. Explaining better:

1 - If you're planning to use different projects, you will be able to configure a single report for each top-level area, splitting the estimations of your team for each area you have separately.

2 - If you decide to group all issues together in the same project, you can have a global report considering all the issues of your team (all top-level areas). Additionally, you could define each top area you have based on the component field, although the report will consider a single global estimation for your team:

Organize work with components 

Let us know if you have any questions.

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events