I made a Loom to show you how Atlassian tools actually work together

[#1]

Jira and Confluence and Compass, oh my! 😵‍💫 Atlassian offers a lot of tools, which is great... if you know how to use them together. 

When combined, Atlassian tools can work together to transform an idea into a fully developed feature. Check out my Loom video where I break it all down in just 13 minutes.

I start with a feature request in Jira Service Management, then move through Jira Product Discovery, Confluence, Jira, Compass, Bitbucket, and Loom to bring the feature to life.

---

Got questions or need some guidance? Join us for our office hours where we can chat about anything Atlassian.

Note: Startups office hours will still be offered during the holiday season, just not as often. If you can’t make one of the offered times, you can always ask us questions in the Startups community group.

---

Peggy’s Picks 🎁

Here are some of my top picks to help you get the most out of Atlassian tools:

• For a bite-sized overview of the products, check out our product intro series!
• This (free!) Atlassian university course on using Jira and Confluence together
• Summer throwback to this 5-minute interview of Cloudflare's Co-Founder on their startup journey with Atlassian

Look forward to connecting soon! 👋

[Ted Henry]

This is a fantastic video Peggy, thanks for making it.

[Juli Bourgeois]

Very useful!  Thank you, Peggy!

[YY Brother]

Awesome demo

[Tomislav Tobijas _Koios_]

Really cool demo @Peggy Graham ! 🙌

One question though - why would you use JSM for feature suggestion intake as you could grant users Contributor roles in JPD and completely avoid having these 'tickets' in two places (JSM and JPD)?

I'm aware that it's logical to use JSM if you'd like to have a proper customer-facing portal, but for ideas/suggestions only, it seems to make more sense to directly add 'customers' to the JPD project (for them to have Atlassian Cloud account and then add them to a Contributor product role).

[Ted Henry]

@Tomislav Tobijas _Koios_ there are probably a number of reason you might want to do it this way.  For example, you may want to combine feature suggestions into a single idea instead of scoring and evaluating them separately.  In this way, feature suggestions submitted through JSM are like "insights" that provide rationale for an idea that's been curated for your workflow.  This could be overkill for many situations, but it would give you flexibility and provide traceability between idea intake and ideas you are seriously evaluating.

Atlassian's Tanguy Crusson talks about this a bit in his video Product Discovery in Action at an Unleash event from a year ago.  The link goes directly to this part of his talk.  https://youtu.be/6P7HBBQyQ5U?t=871

[Tomislav Tobijas _Koios_]

Definitely some fair points there @Ted Henry . I guess it still depends on the use case and the process requirement.

Thanks for sharing the link! (I might just use it as a 'joker' card when discussing this particular topic with clients 😄)

[Islam Mezied]

A very good demo, thanks Peggy!