nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Progress on Intake and Share?

Ben Arundel_ds1fh7

Hey

I am just wondering if there are any updates on the following:

A better method to get requests/ ideas into JIRA product discovery

and

A better ability to share a view externally via the share tab.

The second question about sharing has become urgent as I note I cannot share a view via an iframe

It would be great if you could support an embed option similar to how GitHub works with gists

Any update you can give on these would be great

Accepted answers

Tanguy Crusson

@Ben Arundel We're actively working on the ability to share with people who have an Atlassian account (but not necessarily access to the site or Jira)

Still a decent amount of work to do there but we're hoping to have a first preview available soon.

Thanks for the suggestion for an embed. We currently support that in Confluence but not in public websites. We'll have a look.

As for the other topic - we're currently unpacking how we should tackle it.

All comments

Kyle Mitchell_fkky3k

Agreed that the inability to share views as dynamic iFrames or embeds in other tools is becoming an issue. I have to manually screenshot things and then also post a link. We have competing product tools Aha and JPD and Aha is looking better now because of this. You have this ability already I believe in Advanced Roadmaps.

Richard Muffler_c2ub5n

+1 on eliciting and +1 on sharing Ideas.

For sharing Ideas, it would be great if we could somehow use a field to identify which ideas we'd like to show to our product's users so that they can see what we're planning on doing, as well as give them the ability to add Insights to the ideas. It will help elicit feedback as well as see how many additional users would be interested in that new feature or enhancement.

Then for eliciting new Ideas, it would be cool to give users the ability to create new ideas from that same roadmap type of view.

I would envision this as a "portal" that we could embed in our web app or somewhere in our product. It would show what Ideas we've recently released by quarter, what Ideas we're in-progress working on now, and what Ideas we're thinking about building. Like I initially mention, we would only "publish" specific Ideas in each of these so that we can show customers cool things we've addressed, as well as show Ideas we'd like to get more traction around or additional insight about.

Tanguy Crusson

@Ben Arundel We're actively working on the ability to share with people who have an Atlassian account (but not necessarily access to the site or Jira)

Still a decent amount of work to do there but we're hoping to have a first preview available soon.

Thanks for the suggestion for an embed. We currently support that in Confluence but not in public websites. We'll have a look.

As for the other topic - we're currently unpacking how we should tackle it.

Richard Muffler_c2ub5n

It would also be great to extend that outside of requiring an Atlassian account. As a B2B product, we would like to embed a view of hand picked ideas to customers so that they can see Ideas we've delivered in past quarters, Ideas we're working on, and Ideas we're considering. This way our users can submit Insights on these hand picked ideas, or they can submit a new idea if they don't see something that matches a problem or motivation they would like solved. We would embed that view in our product so that it cannot be accessed outside of having a user login to our product. We're aren't interested in making it fully available for the public to see, we'd want only users in our product to be able to see it.

Richard Muffler_c2ub5n

Productboard does a great job of this with their Portal capability.

Tanguy Crusson

Let me clarify: having an Atlassian account doesn't mean people need access to your xyz.atlassian.net site. It just needs they need to go to id.atlassian.com and create an account. That's it. No need to buy a product or anything.

We're currently working on 2 options:

You add a specific list of people based on their email address
or you decide to share with "anyone with @a-domain.com" email address

But yes, I'm not sure if that will be enough for your use case if you want user access to be based on your own authentication model.

Tanguy Crusson

Yes both Aha! and Productboard are great products and been around for a long time. They're also partners of Atlassian, and integrate with Jira Software.

Rohan Swami

Hi folks,

As Tanguy said already, we're making progress on sharing.

We're also exploring eliciting input from your stakeholders for your prioritisation. If you'd like to discuss your use case and how we might solve for it, please book time in with me on Calendly here.

Ben Arundel_ds1fh7

These are the two high-priority things for me as we go into Q2 to justify using JPD.

1. The ability to share accessible views easily

2. The ability to get Ideas into JPD (A form, a portal etc)

Ben Arundel_ds1fh7

@Tanguy Crusson will this work for instances of the JIRA data centre edition (self-host)

We have a number of Atlassian installs across our org and it would be great if it supported them easily without the need for the licence in ours. (Including the ability to vote)

Michelle Grady_zifu3l

We would like a way for our stakeholders to add customer feedback, feature requests, etc where it's an independent front an Idea.

This allows product to source insights and create an idea or attach any insights that come in that might help with an existing idea.

Right now we have a separate Jira project for our intake process. The Jira Service Desk was not flexible enough to collaborate more on ideas. And I attach any feedback that's relevant to an idea.

Some key things about our intake process is:

We want to make it easy for stakeholders to share any product feedback
Be independent from the ideas that product has in the roadmap, we want to ensure that it doesn't become a laundry list of features to do but insights to inform product what to build
Be collaborative (able to vote, comment, etc) we want to be able to open up conversations and they might just turn into an idea