Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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!


projects, teams & systems (oh my...)

So, time for a Jira spring clean and I'd like some advice on getting things running more smoothly.

Here is what i need to represent in Jira:

  • We have "systems" a,b,c and teams associated with those systems
  • We have a separate Business Analysis team through which all change is filtered
  • We have a separate testing team, through which all testing is pushed
  • We have projects.  Some of which are cross system team, others are not
  • We have feature requests - some of these are also cross system team, others are not
  • We have bug reports

So - my questions are:

Where do epics sit?

should there be projects for all teams?

Should we create a project based around an epic, if it is cross systems?


if there is a good article on this kind of stuff, please point me at it and i'd like to hear some other people's approaches to organising this kind of thing..



Log in or Sign up to comment
AUG Leaders

Atlassian Community Events