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

Using products together

I have a need spanning multiple areas and users, from dev projects to marketing and content development as well as support. Is anyone using Trello (marketing team uses), Confluence (content team asked for), Jira support (IT requested) and Jira Software together? Any benefit to bringing all my needs and applications to one platform rather than multiple different companies?

1 comment

Kudos,: you are the collab support product suite use case. And paying attention to what's common and what's distinct is Exactly The Thing(tm). Think overhead reduction, traceability enhancement, and metaphor.

  • Less Overhead; More Flexibility: Why run several DBMS, identity services, app servers, container engines, etc. Even if you grab a la carte from different sources, now you have more dependency management. Common functions that are the same, just do once.
  • Less Friction; Better Traceability: Can just use the other thing,without another round of setup, and easier traceability. Plus, these user issues (faillures) trace to that design defect (fault), which traces to this correction (chante set), is easier to do if the tools talkto each other.
  • Users and Use: Move between collab metaphors freely. High-presision workflow isn't a knowledge base, isn't a virtual cube farm, isn't.... Slack may be a good virtual town hall, but it's a miserable knowledge base: wrong metaphor.Metaphor abuse is the hidden collab system failure mode. One Tool to Rule Them All -- not so much.

I have driven collab n tool chain integration(s) a kajillion times.

  • One example: "Hey, routing new ops failures (regressions) to the nearest change is a good hack at fixing them faster. Since we own the repository n build, n we're next to the ticket system (that also has defect (fault) tracking), and email ... how about we plug these together .... maybe start with production deployment crash logs as failures routed  in aggregate (candidate faults) to whoever last touched the thing thats crashing?"
  • Another examle: I ponied up about 1/2 an Engineering FTE to manually maintain failure (customer support) to  fault (defect) traceability. It's huge leverage, but I'd much rather have the tech do that for us.

Approaching it this way works.


Log in or Sign up to comment
Community showcase
Published in Confluence

An update on Confluence Cloud customer feedback – June 2022

Hi everyone, We’re always looking at how to improve Confluence and customer feedback plays an important role in making sure we're investing in the areas that will bring the most value to the most c...

115 views 1 2
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