Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

JIRA setup within Development Agency

Hi All,

We currently use JIRA Cloud to manage our internal and external projects and the whole setup feels rather complicated and I'm looking to validate or disprove my thoughts about our current setup.

Current Setup

  • "Global" Project
    • Client Project 1
    • Client Project 2
    • Internal Project 1
    • Client Project 3
    • etc
  • The "Global" project board uses a Filter Query to show all the tickets within the different projects;
    • project in (Client1, Technical, Client2, Internal1, Internal2, etc) ORDER BY Rank ASC
  • There are 17 individual projects in JIRA at the moment, all being shown under "Global"

This setup feels very...clunky and at time, a little unmanageable when it comes to update workflows, permission & notifications etc and it feels like our whole setup could be streamlined and made much more efficient, somehow.

Any tips would be welcome, or advise from anyone that may work within an agency which runs multiple products/clients during a given sprint.

It does feel like I should be moving to a single project, but I'm a little unsure at the moment.

1 comment

John Funk Community Leader Sep 11, 2019

Hi Alex,

What you have described should work. Are there specific things about it that don't allow you to work they way you want? 

I would think that you should be using shared schemes as much as possible - including for workflow. Maybe if you move to that if you are not already doing that, then it will help with maintenance. 

We do something similar with our CRM team - they have multiple projects supported by one Sprint board. 

Hi John,

The current setup works surprising well for us, and all I can think is, "If it ain't broke..." that being said, it just feels like we could be utilising it a whole lot better.

I've moved everything across to shared schemes and workflows which will make management a bit easier.

The next-gen project feature look pretty good, but with this current setup...the next-gen project possibly wouldn't work too well (I could be mistaken and need to read up more on it)

John Funk Community Leader Sep 16, 2019

We don't use Next Gen either, mainly for the reason that we have so many shared schemes. That and we really don't want individuals outside of the Jira Admins changing things. :-)


Log in or Sign up to comment
Community showcase
Published in Marketplace Apps & Integrations

Staying organized with Jira: best practices for a better project management

Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...

232 views 2 1
Read article

Community Events

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

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you