Recently started using JPD? We want to hear about your experience

[#1]

Hello JPD community!

I hope this message finds you well!

I'm Jet, a product manager at Atlassian, and I'm reaching out to connect with customers who are using both Jira Software and Jira Product Discovery. We're eager to learn more about your experiences with these products, particularly how you're leveraging them to plan and prioritise your work effectively.

We're keen to hear about:

1. The specific tasks or workflows you're managing with JPD and JSW.
2. Your initial experiences and challenges when getting started with JPD.
3. How we can enhance the experience to better meet your needs.

If you're open to sharing your insights, I'd love to schedule a 45-minute Zoom chat at your convenience! Please signup here

Looking forward to connecting with you and learning from your expertise!

Best regards,

Jet

[Nikola Perisic]

Hello @Jet !

Thank you for asking us as a community to share our answers. Here are some of my insights so far for the JPD:

• New users might get confused with using the JPD for the very first time - a tour guide feature that is not too long that will hand hold the user and show them how to actually use the product
• Since JPD is made for the team-managed projects, there are some certain limitations within the product, for example having the option to see the reports that would include more product management, example could be found here: https://www.aha.io/blog/report-templates-for-product-managers
• A unique space for the wireframes - here PM's would store all of their wireframes with the option to toggle between the projects (links would solve this easily)
• PRD creation - this would be easily solved by implementing the Confluence pages directly to the JPD projects (this is a huge part of work of a PM, excluding meeting with the stakeholders and dailys with the developers)

These are the features that I can think of for now.

[Omar Chin-Keow]

Loving this product. Very simple but powerful. The ability to customise using every and any metric/ category/ team/ stats I create is very powerful and extremely practical.

I use this frequently as a way to get top level planning done in place of relying on initiatives. I still use initiatives with Atlassian Plans but this is more practical to keep my head in the top-level head space.

Thanks to the team that brought this to us, great job!

O.

[Deepthi_Divakar]

Very easy one ! Nice job Atlassian:)

[Tom Cunliffe]

It's a great tool and it's filled a hole in our team that needed filling. But I don't think we can make it part of our process until project templates / duplications are a thing; we'd need dozens of boards ready to roll out per project and doing that manually is just going to be too much work every single time.

What's the ETA on that feature? I've seen people on here asking for it since 2022 but no sign of it yet sadly....

[Laura Rusenstrom]

For us, JPD could fill a big gap in our process that neither Confluence nor Jira quite met. Most members of our various teams wear many hats, and there's a ton of collaboration about product features and ideas that happens in meetings, Teams chats, emails, leaning over cubicles, etc. We've never had a structured and traceable way to capture, visualize and analyze all of these ideas.

As one of the admins for our Atlassian products, however, I'm struggling hugely with the user management experience for JPD.

• "creators" vs "contributors" seems like a good idea for managing project-by-project roles in JPD, but using those terms also for licensing and administrative purposes adds too much confusion. What even is a "contributor" if everyone in the jira-product-discovery-contributors group has "creator" level permissions?
• Why are there three Atlassian Admin groups for JPD called contributors, admins and users?
• Why does the page for enabling the contributors group warn you not to grant product access to this group, when the system itself granted product access by default and you can't remove it?
• If I change project access to "open", it says that anyone with product access can act as a "creator".  Creators are paid licenses. Everyone who can access Jira has product access to JPD. Therefore, will our entire company, who all use Jira, consume JPD licenses if I open up a project?
• Why do I have to go to Atlassian Admin, general site Settings, and individual project settings in order to not only manage users, but learn about user management?

I'm sure there are answers to all of these questions, but I'm asking them rhetorically to point out that the whole user management system is spread out across too many areas and menus, the terminology is not always clear, the Atlassian Admin user groups don't align with the way the licenses are described, and it's just been a generally exhausting experience trying to learn my way through it.

I would love to see a complete overhaul of the way users are identified, described and managed in JPD. I think this was maybe an attempt to make it highly customizable, but like the whole "issue types vs issue type schemes vs issue type screen schemes" thing in Jira, it just winds up being way too complex.

I just want something simple and straightforward where I can set who has permission to create and configure JPD projects, separate from who can create and interact with ideas, and the confidence to know that I'm not going to accidentally cost us a license when I add someone to a contributors group that actually gives creator access.

The pricing is also not sustainable for us. We want everyone who creates an idea to also be able to label that idea with the goals and product areas it relates to, but at $10 per user per month, JPD is more expensive than Jira (standard) and absolutely off the table budget-wise. I can't have three people entirely responsible for labelling, estimating, prioritizing and managing ideas for an entire company. The breakdown of features that cost money vs those that don't seem wholly unsuitable for small to mid-size organizations.