youngmon/atlassian-qna huggingface dataset:
Proposal: Add functionality to integrate ProductDiscovery and Confluence
Asked by Tashiro, Hideyuki:

We would like to use Confluence as ProjectPage in ProductDiscovery project as in JIRA project. Currently, we can only link within an idea, so we would like to improve this.


Answers:
author: Rohan Swami
body: Hi [@Tashiro, Hideyuki](/t5/user/viewprofilepage/user-id/4995061) , thanks for sharing your suggestion. Can you share a bit more detail about how you would like this to work? Is it one Confluence Project Page that maps to an entire Product Discovery project?
Is it possible to filter within a view by a text field?
Asked by Mar?a Ferre?o:

Hello,  
I am faced with the following scenario, see if you can help me.  
- Currently, in the JPD list view, I have the "filter" option.  
- This is great because it is very easy for users to select a Jira field and "filter" the information.  
- But what about text-type fields? They are not available for filtering.  
- In a normal filter (in Jira Software for example) I can select a text field, for example Summary and look for tasks that contain in their summary some word.![filter by summary.png](https://community.atlassian.com/t5/image/serverpage/image-id/287283i3ABFAE7F8B761FC5/image-size/large?v=v2&px=999 "filter by summary.png")  
- Is there any way to do the same in JPD?

Thank you very much ?


Answers:
author: Rohan Swami
body: Hi [@Mar?a Ferre?o](/t5/user/viewprofilepage/user-id/4761586) filters are based on field values that can be selected, for example select and multi-select fields, or basic functions on number fields. To create a filter, move these field values to a select or multi-select field.

Alternatively you could use the search function at the top right of the view **Find an idea in this view** to find ideas, though the results will not persist as a filter.

comments: author: Mar?a Ferre?o
body: Thank you for your quick response [@rohan](/t5/user/viewprofilepage/user-id/4255731)  
That's what I thought ?


author: Taronish Pithawala
body: I had this same question, and the JPD team told me this was not currently possible. I really hope that this functionality is added soon!

comments: author: Mar?a Ferre?o
body: Hopefully, because it would be very useful for users ??
Automation: Clearing REACTIONS & MENTION Fields
Asked by Sebastian Pechhold:

Hi,

we try to set up an automation with trigger schedule which clears a specific reaction and mention field. It seems that these to field types are not supported. Is there a work around to achieve it?

![Screenshot 2023-10-17 at 11.33.40.png](https://community.atlassian.com/t5/image/serverpage/image-id/286666i3FE90457011EBBFD/image-size/large?v=v2&px=999 "Screenshot 2023-10-17 at 11.33.40.png")


Answers:
author: Hermance NDounga
body: Hello Sebastian,

Indeed these fields types aren't supported in Automation yet as per [Known limitations of Jira Product Discovery.](https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Known-limitations-of-Jira-Product-Discovery/ba-p/2069648?)

We will explore support for these fields, but it is not prioritized on the roadmap yet.

There is no workaround at the moment, bu could you please elaborate more on your use case?

Cheers,

Hermance

comments: author: Bill Sheboy
body: Hi [@Hermance NDounga](/t5/user/viewprofilepage/user-id/430755)

FYI the link you provided is broken. Is this the one you wanted for the known limitations?

<https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Known-limitations-of-Jira-Product-Discovery/ba-p/2069648>

And...I just tested and although an example field of Reaction type is returned by the REST API to check for things automation supports, the value is always null in the response. That behavior might confuse people into thinking it is sort-of supported.

Kind regards,  
Bill


author: Hermance NDounga
body: So weird for the link; thanks Bill!

Full disclosure here: We are in the middle of a refactoring of the fields - to improve on performance, and make sure we can scale. so basically, their behaviour might change very soon, and that's also why we aren't too sure yet how to integrate them with automation - because the way they are stored/built can change very soon.

So yup it's not for today :) but you understand why we don't really optimize for their current behaviour.
Including "Description" field in CSV export?
Asked by Andy Lutz:

Hello!

The ability to [export a view to CSV](https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Anyone-able-to-export-Impact-Impact-Score-to-Domo-or-as-a-CSV/qaq-p/2469978) is very helpful for my org, as often we want to capture a "snapshot" of the roadmap at a certain point in time.

It looks like the export functionality is limited to only capturing fields that are enabled in the view, which means it's not possible to export the "Description" for the item (since that cannot be enabled as a field in the view).

I'm wondering if there's any way to include the "Description" in the CSV export, or if this is planned functionality?

Thanks!

Andy


Answers:
author: Hermance NDounga
body: Hi Andy,

basically this functionality is a WYSIWYG exporter, so it's not planned to have the description in it (especially since the description can be _very_ long and including a lot of formatting, attachments and links, which aren't suitable to the csv format.

The main usecase was to be able to quickly get and export to then do even more complex operations, such as advanced filtering, or pivot tables, based on formula values etc.

Could you please elaborate on your use case?

<br />

In the meantime, you can display a short text field , such as "public description, which will be useful also for timeline views or when we release stakeholder views.

Cheers,

Hermance

comments: author: Andy Lutz
body: Thank you Hermance, that was what I assumed and I appreciate the clarification.

For my use case specifically, I have several PMs that want to share an export with other stakeholders who do not have access to their Project. However, without the Description, the stakeholders don't have the additional context needed to make the export useful.

I'm curious when stakeholder views is planned for release?

That might solve part of this issue.


author: Hermance NDounga
body: Hey Andy,

Yeah for what you describe, sharing static csv documents isn't ideal anyways. Stakeholders view is currently EAP, so I cannot provide you with an exact date, but it should be in like 3-6 months :)


author: Sebastian Pechhold
body: Descriptions will be exported as well. After export you can check the file and before importing them, you can validate all data. It is not really easy but feasible.


Tags: csv

export
Moving ideas from one JPD to another (including insights and field values)
Asked by Christina Detlefs:

Hello,   

I have multiple JPD projects that are set up the same way (Field names, field types etc). We want to be able to keep some projects as our ideas backlog and then move over to another JPD project for planning and reporting.   
We dont want to import via xls file as it takes too long and we may just want to move 1-2 ideas at a time.

I notice there is a 'move' function however the field values dont copy across.

Is there a way we can move ideas as well as all the values across to another project? Or if this feature is coming up, do we know roughly when it will be available? This will be really useful in our organisation!

Thank you!


Answers:
author: Hermance NDounga
body: Hi Christina,

We don't recommend to export ideas via xls, it has missing fields, and also I don't think you can only export just one project in that way.

Unfortunately, there is no good solution at the moment. If you use the move feature, values aren't copied, but comments and insights are kept.

My recommendation would be to use the export as .csv button, available in any view. I will keep your values and comments, but not insights.

![Screenshot 2023-10-17 at 09.40.15.png](https://community.atlassian.com/t5/image/serverpage/image-id/286633i31BE32B066614C24/image-size/large?v=v2&px=999 "Screenshot 2023-10-17 at 09.40.15.png")You can import them back using the csv import, under "System"

![Screenshot 2023-10-17 at 09.41.33.png](https://community.atlassian.com/t5/image/serverpage/image-id/286635i8C43CCB37BB6A746/image-size/large?v=v2&px=999 "Screenshot 2023-10-17 at 09.41.33.png")

comments: author: Parker Dow
body: I would use this immediately as a feature. I have two boards - one for triaging incoming ideas and another for developing these ideas once they are committed. At the moment I need to copy/paste all the values moving from one to another. [@Hermance NDounga](/t5/user/viewprofilepage/user-id/430755)   

Having the ability to bulk move ideas would be great.


author: Bailey Walatka
body: Is there any update on when a feature to move ideas between Discovery Boards might be available? We would definitely use this daily, I've tried every workaround provided on this forum and hit roadblocks every time.


author: Omer Meshar
body: Hi [@Christina Detlefs](/t5/user/viewprofilepage/user-id/4897407) ,

I wanted to merge a few JPD projects into one, and succeeded in doing so using both Merge and Export/Import. See the discussion [here](https://community.atlassian.com/t5/Jira-Product-Discovery/What-is-the-best-way-to-merge-multiple-JPD-projects-into-one/td-p/2369335)

I hope this helps you out.

Omer
Default Add User forces extra Payment
Asked by Ravid:

When inviting a user to Atlassian, the default of "Product Discovery" is "User" which causes extra Payment. How can we change it?   
![user.JPG](https://community.atlassian.com/t5/image/serverpage/image-id/286142iB62E628D62614C2E/image-size/large?v=v2&px=999 "user.JPG")


Answers:
author: Nick H
body: Hi [@Ravid](/t5/user/viewprofilepage/user-id/4927950) ,

Please reach out to [JPD support](https://support.atlassian.com/contact/#/), and we will be able to assist with deselecting JPD from being a default product new users are added to.

Unfortunately this cannot be managed on your end, but there's a feature request for this functionality: [Ability to uncheck products by default in Product Access when inviting new users](https://jira.atlassian.com/browse/ID-8059)
Why can't I search for Delivery issues from certain projects?
Asked by Marc Gilbert:

Hello,

I can search for a project just fine, but I can never get the issues that I need. Am I not allowed to search for issues from Team-managed projects? Do I need to be specifically invited to these projects or something?

I seem to be able to add company-managed issues just fine.

Any ideas?

Thanks!  

EDIT: After some testing, I can actually find some Team-managed project issues, but only some.


Answers:
author: Dave Mathijs
body: Hi [@Marc Gilbert](/t5/user/viewprofilepage/user-id/5338462) welcome to the Atlassian Community!

This may indeed be permission related.

Tip: Don't use team-managed projects, it'll will always lead to limitations in the end when sharing or reporting on information across projects.

comments: author: Marc Gilbert
body: Hey [@Dave Mathijs](/t5/user/viewprofilepage/user-id/2662590)

Thanks for the reply :) Yeah seems to be the case! I think we're slowly moving to company-managed for everything thankfully, so should be a bit better.

Cheers!


author: Dave Mathijs
body: [@Marc Gilbert](/t5/user/viewprofilepage/user-id/5338462) Thanks to click the green "Accept answer" button if it helped you answer your question.


author: Marc Gilbert
body: Ah ha! I think I know why: I do not have the ability to create issues within those specific projects. If someone can confirm this is the case, that would be helpful :)
Linking ideas from two different Jira Product Discovery projects
Asked by Guillaume Govers:

Hey,

We have started using Jira Product Discovery and have two distinct Jira Product Discovery projects used by two separate teams.

However, some of the ideas on both projects are interrelated and require both teams to navigate both projects. To enable this in a simple way, we wanted to link an idea from JPD project A to an idea from JPD project B. This would clarify and enhance navigation between the projects.  

We have tried using both the standard "Linked Issues" field and the JPD-native "Delivery Issue" to create this link. However, neither of these is functional. When adding the link to an idea it simply says that the "Issue could not be found".

Is this issue a consequence of JPD being team-managed projects? Or is there a configuration step I am missing to enable this feature?

Thank you for your help,

Guillaume


Answers:
author: Nick H
body: Hi [@Guillaume Govers](/t5/user/viewprofilepage/user-id/4945148) ,

After testing, it should be possible to link ideas between different JPD projects using the [**Link issues**](https://support.atlassian.com/jira-service-management-cloud/docs/link-subtasks-issues-and-pages-from-the-new-issue-view/#Link-issues) button:

![link1.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/286020i9F9E6E783AFC83AD/image-size/large?v=v2&px=999 "link1.jpg")

![link2.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/286015i7FACD49F5625DADC/image-size/large?v=v2&px=999 "link2.jpg")

Maybe it's a permission issue that is causing the error and now allowing you to link between jpd projects. I don't believe it is related to JPD projects being team-managed.

As for [creating delivery issues](https://support.atlassian.com/jira-product-discovery/docs/create-a-jira-issue-from-jira-product-discovery/), these cannot create a delivery under another JPD project. They can only create deliveries under JSW, JSM and JWM projects at this time.


author: Guillaume Govers
body: Hey [@Nick H](/t5/user/viewprofilepage/user-id/2540930) and [@Bill Sheboy](/t5/user/viewprofilepage/user-id/1685313)

It was indeed a permission issue.

I didn't realize you needed to have a "Creator" role in both projects. I suppose that makes sense since I am modifying ideas in both projects at the same time when adding a link.

Thank you both for the swift replies,

Guillaume


author: Omer Meshar
body: We also started with a couple of JPD projects, but we realized that there are too many things we needed to share between the teams, so we switched to a single project for all teams.


author: Bill Sheboy
body: Hi [@Guillaume Govers](/t5/user/viewprofilepage/user-id/4945148)

When you tried Linked Issues and note that "neither of these is functional", what do you observe happening?

I just tried linking ideas in two different JPD projects and it worked.

Kind regards,  
Bill
What is the import format for "Delivery Progress/Status" fields in JPD?
Asked by Mart Postma:

Hi all,  

I am trying to import many new ideas into JPD with a CSV file. In JPD, I am using the "Delivery Progress" and "Delivery Status" fields. When importing, I just pasted the Epic issue-id like KEY-123 into the column of these fields, as that is also working for the "Link "Relates"' field in JPD.  

However, during import, JPD doesn't accept KEY-123 format and expects a number (I guess?).   

So, how am I able to import data from Jira Cloud into these two JPD fields with a CSV file?   

Thanks!


Answers:
author: Rohan Swami
body: Hi [@Mart Postma](/t5/user/viewprofilepage/user-id/5313648) the delivery progress and status fields can't be imported as they are calculated fields based on the linked issues. I haven't been able to find a guide to import linked issues unfortunately, sorry about that!

comments: author: Mart Postma
body: Hi [@Rohan Swami](/t5/user/viewprofilepage/user-id/2842658)

Thanks for your answer. How come that when I add them manually in JPD, I also use the KEY-123 from another project to link it to a delivery status, but not when I import the key? And it does work in a similar fashion for linked issues such as "Relates" when I import the key with a CSV file.  

I understand that for now there is nothing to change here, but just some feedback for development ;)   

Thank you!


author: Rohan Swami
body: I believe it's because the logic here is that issues used for delivery progress calculations are a special type of issue link, we don't look at regular issue links to calculate delivery progress.
Attributing customers to ideas
Asked by Owen Friedrich:

We have a need to track one or more customers to an Idea so we can generate reports that show "We completed x items for Customer A" or "We have x items on the roadmap for Customer A".

Using a multi-select dropdown is an option but we have over 20k customers so this doesn't scale well and I am not aware of an easy way to import a list that large into a dropdown. (or keep it updated).

Insights seems to be another option but requires the user to copy in the Account from Salesforce. We are also not sure if we can accurately report on this data in comparison to a normal JPD field.

How are others solving this need?


Answers:
author: Diala Al-Khawaldeh
body: this is a much needed feature!


author: Ted
body: Maybe using categories for types of customers would be more effective, I'm not sure how useful having 20k different customer labels attached to various ideas in JPD is going to be...


author: Ylan Muller
body: Wanted to chime in and say that this is very much needed. With Jira Software we use an integration from AppFire for Salesforce x Jira to associate accounts and opportunities with tickets, but it does not get surfaced in Product Discovery. With JPD we are currently tracking by plugging the affected customers account URLs from Salesforce in Insights, which is messy.
Gathering Team feedback
Asked by Tim Causer:

How do you get/allow the Team to submit their own opinion of effort and goal impact on ideas, such that we can collate those votes, understand outlier opinions and get the best idea of those metrics?


Answers:
author: Rohan Swami
body: Hi Tim, 2 recommendations for you here:

1. Teams get a lot of value out of discussing effort and impact estimates, it's not so much the number that matters but the resulting discussion of why people have different estimates, so the most value is achieved synchronously.

2. An asynchronous way of doing this would be to add these estimates as comments to the idea.

comments: author: Tim Causer
body: Thanks Rohan.  

I agree about the discussion and that was intended but not all voices get heard, the post your opinion idea ensures participation...   

Regardless, we will have to use the comments for this purpose - a feature to consider perhaps (seems a competitor has it (below!))


author: Victor Forest
body: Hi Tim,

[airfocus' Priority Poker](https://youtu.be/6aD3-xLbh1g) enables you to achieve this, as you can gather stakeholders to reach a consensus on product priorities.

Let me know how this resonates.
Funding Request Template for Jira Product Discovery
Asked by Kartik Lunkad:

Hi!

Internally within my organization, I'm proposing the usage of Product Discovery, and wanting to move from Free to Standard Tier.

Do you have any templates or presentations explaining why JIRA Product Discovery is compelling and valuable?

Any content on it would be useful :)

For context: We do use JIRA fully with engineering teams, so everyone is all-in there.


Answers:
author: Chris Hall
body: Hey [@Kartik Lunkad](/t5/user/viewprofilepage/user-id/5332730)! Thanks for your question and glad to hear you're thinking of adopting JPD!

We do have several resources you can share with your team:

* Our "Introduction to Jira Product Discovery" demo -- available [on demand,](https://www.atlassian.com/software/jira/product-discovery/demo-on-demand) or you or your colleagues can sign up for one of our [upcoming live sessions](https://www.atlassian.com/software/jira/product-discovery/demo) (they happen every two weeks).
* We also have an upcoming webinar around discovery best practices hosted by our Head of Product that I think would be interesting to you. You can register [here](https://www.atlassian.com/webinars/software/how-to-uplevel-your-product-discovery-practice-with-jira-product-discovery).

I also have some print resources if you would prefer to share those (a copy of the deck we use in the demo and a one-pager). If you email me at chall@atlassian.com, I can send those over to you (unfortunately can't attach items in the Community!)

Thanks!
Odd date mapping when importing CSV export from Jira Cloud to Jira Product Discovery
Asked by Mart Postma:

Hi all,   

I'm using the Jira Cloud Excel plug-in to query some data from both Jira Cloud and Jira Product Discovery. When I export a CSV file from Jira Cloud, the date format in Jira Cloud (blue) is different than the date format in JPD (red).   

Any suggestions/ideas on how to change the date formatting of JPD (red) such that it matches Jira Cloud's format?   

![2023-10-04_11-24-14.png](https://community.atlassian.com/t5/image/serverpage/image-id/284386i79C2EB044132F559/image-size/large?v=v2&px=999 "2023-10-04_11-24-14.png")


Answers:
author: Rohan Swami
body: Hi [@Mart Postma](/t5/user/viewprofilepage/user-id/5313648) the reason the date format of JPD is different is because JPD allows you to choose a 'fuzzy' date like a month or quarter, which is a string under the hood.

You could manipulate this once you're in excel with formulas like below.![Screenshot 2023-10-05 at 3.16.34 pm.png](https://community.atlassian.com/t5/image/serverpage/image-id/284705i6FBB734F4EEBB156/image-size/large?v=v2&px=999 "Screenshot 2023-10-05 at 3.16.34 pm.png")
Non-required field on ?Create issue? panel doesn?t persist between creating delivery tickets?
Asked by Andy Lutz:

Hi All,

Currently when creating a new delivery ticket in JPD, the "Create issue" panel pulls in all "required" fields as I would expect:

![Screenshot 2023-09-27 at 11.00.20 AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/283305i10628F41B40E5B0B/image-size/large?v=v2&px=999 "Screenshot 2023-09-27 at 11.00.20 AM.png")

I can then hit the "three dot" menu to add non-required fields when submitting the ticket. For example, this field called "Labels":

![Screenshot 2023-09-27 at 11.01.52 AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/283306iF9EF1E82C60D5954/image-size/large?v=v2&px=999 "Screenshot 2023-09-27 at 11.01.52 AM.png")

After I create the issue, the problem is that when I go to create another Delivery ticket, the "Labels" field is not pulled in, only the required fields.

For my teams this is a challenge, since some of our software projects have some fields that are required for some teams, but not others. As a result, they're not "required" fields. This means that to create a delivery ticket from JPD, some teams each time would need to go into the three dot menu and manually add the fields they need to submit along with their ticket.

I'm wondering if there's a way to get these "non-required" fields to persist in between creating delivery tickets in JPD?

Thanks!

Andy


Answers:
author: Rohan Swami
body: [@andy](/t5/user/viewprofilepage/user-id/4934907) if I understand correctly, you're looking for a 'remember my last selection' feature when creating delivery tickets. This would remember that you made the field visible last time, but it won't apply this to any other user. Do I have that right?

comments: author: Andy Lutz
body: Hi [@Rohan Swami](/t5/user/viewprofilepage/user-id/2842658), yes you've got it. Per user "remember my last selection" would be great for teams who share a project, but might need to use slightly different fields when creating delivery tickets.


author: Rohan Swami
body: Got it. We don't have a feature like that at the moment, but I'll record this feedback for us to consider in the future.