Atlassian Team members are employees working across the company in a wide variety of roles.
January 20, 2025 edited
Hello everyone!
I'm excited to announce that this feature is now available to everyone. The issue we encountered was due to a reset in our feature flag, but I'm happy to report that it has been resolved.
Thank you for your patience and understanding during this delay. We appreciate your support!
I love the idea of being able to link the Jira Product Discovery to the Jira Plans,
The issue for me is though that the Jira Plans are not covered by the Publish and share with those with "Contributors" permissions.
The Plans are the things i would like to share with my business and they dont have the ability to see them yet, Are Atlassian looking to make the Jira Plans Publishable similar to Jira Product Discovery?
Atlassian Team members are employees working across the company in a wide variety of roles.
March 24, 2025 edited
Hi @Jack Young , we don't have plans for that as yet. However we're keen to understand this more.
So these people in your business you'd like to share Plans with, don't have Jira access, so can't access Plans.It would be great for us to understand these stakeholders roles. Also, while they are only in Jira Product Discovery and not Jira, how would viewing the Plans benefit them? And how often do you think they will be reviewing Plans? Thanks!!
@jet I've been playing around with this for my team as well, and I have the same issue as those above where I am not able to link to Ideas from within an Eipc nor do I see a Group By option in the View Settings of my plan. I realize it's been a few months since this went out to everyone, so curious if you can help.
Just trying to tap into a question I regularly see here in the forums on how delivery progress should / could properly be tracked. It seems as if the integration puts a JPD Idea in a very similar position as an initiative work type would be if you're using Plans in Jira alone (without JPD).
Ideas get connected to (delivery) epics, in all examples shown. That seems to create some sort of redundancy and the implementation is different. For JPD ideas, idea is a different field. In Jira, linking an epic to an initiative would go through the parent field.
Is anything being done or considered to integrate this better? Or any recommended practices to avoid the need to manage the same information in different places / in different ways?
35 comments