Hi all, we've been experiencing trouble as a business because we always tend to have one project that ends up being a bit of a dumping ground.
I'm talking about internal facing projects - we use a separate project for public facing support.
We develop 3 products. Initially we used one project for development of all products, alerting, everything. This was awful unsurprisingly so I swiftly put an end to it splitting it up into one project per product, and also an alerting project.
My question essentially is how granular do you go with your projects? We now have an SRE project, so in this project goes tickets regarding the deployment pipeline, monitoring, infrastructure, the usual SRE stack. We find it has become a bit of a dumping ground, or certainly the quantity of issues is pretty unmanageable.
So would you split out your projects even further or is this normal? Particularly interested in how many projects people are using and particularly how they are using them for things like an SRE team which has a hand in many things across multiple projects.
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