youngmon/atlassian-qna huggingface dataset:
Filter by Status does not allow selection of items in check-box
Asked by p_geremia:

I am trying to apply a filter on the ideas in list View but if I select the Status field I am not able to tick any of the available items in the check-box, am I missing something?


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

We may need additional clarification on the issue you are running into.

When filtering on the Status of ideas, you should be able to select which appear in the view like so:

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

There's also the option to Group by Status which may be more helpful. No checkbox needs to be selected and instead, all ideas will appear in the view categorized by the field selected through a drop-down. The fields can also be rearranged in the view:

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

comments: author: p_geremia
body: [@Nick H](/t5/user/viewprofilepage/user-id/2540930)thank you for your help! I confirm that now everything works fine and I am able to use the checkbox using the Filter option, not sure why it did not work in the first place.
Custom fields are not visible when Published
Asked by Florian:

Hi !  
I created 2 custom fields for the Ideas view:![2024-03-27_14h55_40.png](https://community.atlassian.com/t5/image/serverpage/image-id/314830i46ECC65F6EE06C67/image-dimensions/452x215?v=v2 "2024-03-27_14h55_40.png")

When I publish this view, I cannot see these 2 fields.

![2024-03-27_14h58_06.png](https://community.atlassian.com/t5/image/serverpage/image-id/314831iCA720BA3EC78122B/image-dimensions/447x151?v=v2 "2024-03-27_14h58_06.png")

Am I missing something?


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

As [@Dexter de Vera](/t5/user/viewprofilepage/user-id/4657717) mentioned, there are some limitations to which field(s) can be published at this time. This is mentioned in our documentation here: [Publish views](https://support.atlassian.com/jira-product-discovery/docs/share-project-views/)

There should also be a warning like in the screenshot below of which field(s) cannot be published:

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


author: Dexter de Vera
body: Hi [@Florian](/t5/user/viewprofilepage/user-id/5418933) and welcome,

The fields you created is a custom formula (special field) that cant be publish a view .

List of special fields:

* Atlas goals

* Atlas projects

* Votes

* Reactions

* Custom formula

* Number of linked issues

* Number of insights

comments: author: Dexter de Vera
body: Hi [@Florian](/t5/user/viewprofilepage/user-id/5418933) , can you accept my answer too.. Thank you!


author: Florian
body: [@Nick H](/t5/user/viewprofilepage/user-id/2540930) , [@Dexter de Vera](/t5/user/viewprofilepage/user-id/4657717)   
Thank you for your answers! That's clear

Do you know if there is a plan to improve that and make these fields available?

comments: author: Dexter de Vera
body: I dont think there will be an update for those fields in Product Discovery.  
Here you can view Atlassian roadmap.
> <https://www.atlassian.com/wac/roadmap/cloud?selectedProduct=jpd>
Automation to chance a status based on a custom field having >= a number
Asked by Penny Schenkkan:

I have the Impact Score field in my Discovery board. I want the Status of the issue to change with the Impact Score is equal to or greater than a certain number (and vice versa, when it's equal to or less than a certain number).

Anyone know what the automation steps would be?


Answers:
author: Nick H
body: Hi [@Penny Schenkkan](/t5/user/viewprofilepage/user-id/5455778) ,

I unfortunately don't think the use case is currently possible since Formula fields are not support with automations as mentioned in this post: [Known limitations of Jira Product Discovery](https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Known-limitations-of-Jira-Product-Discovery/ba-p/2069648)
>
> #### **Project Automation is only partially supported** {#toc-hId-319963327}
>
> You can use Project Automation in Jira Product Discovery projects, with the following limitations:
>
> * Some fields aren't supported in automation rules, in particular:
>   * **Formula fields**
>   * Vote fields
>   * Insights field
>   * Delivery progress/status fields
>   * People fields

comments: author: Penny Schenkkan
body: Thank you Nick! That explains a lot!

Any idea if/when they will be supported?


author: Bill Sheboy
body: Hi [@Penny Schenkkan](/t5/user/viewprofilepage/user-id/5455778)

What have you tried thus far to solve this need?

If you started an automation rule and it is not working as you expect, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas.

If you have not started a rule, please note that successfully using automation rules requires learning and experimentation. I encourage you to try to create the rule, and if you run into challenges to post your rule and explain what is not working.

To get you started on creating your rule, the rule would could be triggered on a change to your Impact Score, and use a condition to decide if the issue should transition the status value. Please refer to these documentation and example rules to help:

* <https://www.atlassian.com/software/jira/guides/automation/overview#what-is-automation>
* [https://www.atlassian.com/software/jira/automation-template-library#/rule-list?systemLabelId=all\&page=1\&pageSize=20\&sortKey=name\&sortOrder=ASC](https://www.atlassian.com/software/jira/automation-template-library#/rule-list?systemLabelId=all&page=1&pageSize=20&sortKey=name&sortOrder=ASC)
* <https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/>

Kind regards,  
Bill

comments: author: Penny Schenkkan
body: Hi Bill, I've been trying to build an automation but don't even know how to start for what I need. The language in the automation builder is not intuitive for me and I honestly haven't found the links you sent (which I previously reviewed) to be helpful enough. Thus my question to the community.
Jira Product discovery- Export
Asked by Monica Arun Kumar:

How to export all the data from JPD to excel/ word? Thanks


Answers:
author: Nick H
body: Hi [@Monica Arun Kumar](/t5/user/viewprofilepage/user-id/5333218) ,

You can export your data / JPD ideas by following these steps: [Export Jira Product Discovery data to CSV, Excel and GSheets](https://support.atlassian.com/jira-product-discovery/docs/export-jira-product-discovery-data-to-excel-and-gsheets/)

Personally I would suggest following the **Export data to Excel with the native app** steps, and exporting via the Filters tab where you can select the *all fields* option:

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


author: Nick H
body: Hi [@Monica Arun Kumar](/t5/user/viewprofilepage/user-id/5333218) ,

You can export your JPD data / ideas by following these steps:

[Export Jira Product Discovery data to CSV, Excel and GSheets](https://support.atlassian.com/jira-product-discovery/docs/export-jira-product-discovery-data-to-excel-and-gsheets/)

I personally would suggest following the **Export data to Excel with the native app** steps where you export the ideas via the Filters tab, and select the *all fields* option:

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


Tags: cloud

jira

jira-software-cloud
How do I link JPD projects to Atlas projects one-to-many?
Asked by Bryce York:

I'm wondering how I can best implement a one-to-many relationship between my JPD project and 1 or more Atlas projects.

I tried linking the JPD project, but I only see Jira and JPD issues.  

I also tried a dedicated attribute, which works great for 1:1 but what we really need is one-to-many.

Thanks in advance!


Answers:
author: Rohan Swami
body: [@Bryce York](/t5/user/viewprofilepage/user-id/4837330) Could you share a bit more about how you've set things up? Generally speaking an idea in JPD is an initiative, big or small; a project in Atlas is used to track that initiative.

These initiatives contribute to goals, and sometimes a single initiative can contribute to multiple goals which is why we've support 1:many for ideas to Atlas goals.

comments: author: Bryce York
body: Hi [@Rohan Swami](/t5/user/viewprofilepage/user-id/2842658) -- <https://www.loom.com/share/bdd6bf0af6c94c56b37f3b21172ea162?sid=fbb510aa-d798-4524-8157-ad98e3480482>

Put this together for you, hope it helps. Apologies for it being a bit lengthy.


author: Rohan Swami
body: Thanks so much for that context, Bryce. I've added it as an insight for our internal JPD project. How's this as a workaround? You can create URL fields for each 'phase' of Atlas ticket. That way you can create views for each team (Design/PM) showing where all the work is at.

![Screenshot 2024-03-26 at 4.21.54?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/314585iB5C630FCF44B4512/image-size/large?v=v2&px=999 "Screenshot 2024-03-26 at 4.21.54?PM.png")


author: Bryce York
body: [@Rohan Swami](/t5/user/viewprofilepage/user-id/2842658) I think that workaround will suit our needs. Thanks!


Tags: atlas

feature
Deferment Date automation error
Asked by Penny Schenkkan:

I followed the instructions to set up the resurfacing automation using the Deferment Date field but I'm getting this error:  
"Unknown fields set during edit, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored -  
Deferment Date (customfield_10097)  
No fields or field values to edit for issues (could be due to some field values not existing in a given project):  
BPD-200"  
And here's the setup of the automation:  
![2024-03-25 08_31_05-Audit log - Automation - Boost Product Discovery - Jira.png](https://community.atlassian.com/t5/image/serverpage/image-id/314218iC90E930177DAC2FF/image-size/large?v=v2&px=999 "2024-03-25 08_31_05-Audit log - Automation - Boost Product Discovery - Jira.png")  
Side note: please use plain English with me, I'm new :)


Answers:
author: Moazzem Hossain
body: Would love to ask support as well.

comments: author: Penny Schenkkan
body: Will let you know what they say.


author: Penny Schenkkan
body: Here's their response, you will need to reach out to them.

We've looked into the issue further, and it appears that your site's system user (Automation for Jira) didn't have access to Jira Product Discovery.  
This led to the issue you observed, in which the automation rule couldn't find the \`Deferment Date\` field.  
The access should be granted by default to system users when JPD is added to your site, but that's not the case.

That said, we've helped to make the necessary update, and the Automation rule should now be able to access the JPD project's fields.


author: Stephen_Lugton
body: Deferment Date is a custom field not one of the standard fields for Jira, as can be seen by the words (customfield_10097).  

So my first question would be how is Deferment Date set up? By which I mean is it a field you've added in Jira Product Discovery, or is it a custom field set up in Jira Software?  

The error message looks like it's a Jira Software custom field that is only available to issues in Jira Software not in Jira Product Discovery.  

You can check whether this is a Jira Software custom field by checking to see if it's available on a Task, Story or Epic, if so it won't be available for JPD.

comments: author: Penny Schenkkan
body: Hi Stephen, it's actually the same issue in this thread: <https://community.atlassian.com/t5/Jira-Product-Discovery-questions/I-can-t-get-the-resurface-date-automation-to-work/qaq-p/2559993>

I will reply there so as to not have another thread going. Thanks though!
Use Delivery Tickets Timefields in JPDs timeline
Asked by Antal Vig Communardo:

Hi Folks,   
I'm not sure if I'm just hallucinating or wasn't there some kind of EAP for Jira Product Discovery to show the Delivery Tickets Start/Due date in JPDs timeline.   
We want to see if we could manage the ideas and the implemenations for Multiple client projects from one JPD board and that would be very handy for that. As we don't need any extra Apps for that.


Answers:
author: Rohan Swami
body: Hi [@Antal Vig Communardo](/t5/user/viewprofilepage/user-id/3544439) yes we do support this, it's already in GA. [Here's a Loom demo](https://www.loom.com/share/8220e4ca892d478ebf57bff822e53ffb) on how to set it up.
What is the best way to create custom workflows in a Discovery Project?
Asked by Jonah Johnson:

For example, a project requires three certifications each with multiple steps involved. I'd like to create three custom workflows to move the current status as each step is achieved, and link it to the discovery project, or be able to create them within the discovery project.  

possible? What are my options?


Answers:
author: Walter Buggenhout
body: Hi [@Jonah Johnson](/t5/user/viewprofilepage/user-id/5133826),

Jira Product Discovery are specifically designed to manage *ideas*, gather insights for them an prioritise product / idea decisions. The work that follows the ideation process (the delivery), is then best managed in a Jira Software project, by linking epics to the ideas in JPD.

JPD is built on top of team managed projects, so configuring workflows is exactly the same as in a team managed software project. You can edit the existing workflow from *project settings \> issue types*.

See [this support article](https://support.atlassian.com/jira-product-discovery/docs/manage-your-discovery-project-workflows/) for more information.

Hope this helps!


author: Ste Wright
body: Hi [@Jonah Johnson](/t5/user/viewprofilepage/user-id/5133826)

Do you mean in Jira Product Discovery, or in Jira Software?

A Company-managed Jira Software Project would be well suited for this, as boards can better manage multiple workflows.

---

You then need to...

1. Create the certifications as [issue types](https://support.atlassian.com/jira-cloud-administration/docs/what-are-issue-types/)
2. Assign them to an existing [issue type scheme](https://support.atlassian.com/jira-cloud-administration/docs/what-are-issue-type-schemes/), or create a new one
3. Assign the issue type scheme to your Project (if needed)
4. Create a workflow per certification, and a workflow scheme for them to be housed in (which also needs to be assigned to your Project). Instructions for all of these can be found [here](https://support.atlassian.com/jira-service-management-cloud/docs/overview-of-jira-cloud-workflows/)

---

Let us know if you need any more specific instructions!

Ste


Tags: cloud

jira

jira-cloud
How do I assign idea back to the contributor in JIRA Product discovery?
Asked by Hariharan Y:

We are trying out the JIRA Product discovery module. And I am wondering how to assign an issue back to a contributor? This situation arises when more information is required from the contributor and would need to routed back to them to provide the information and move the idea to the next step. Is this possible? If not, what is the workaround? Thank you.


Answers:
author: Tanguy Crusson
body: Hi [@Hariharan Y](/t5/user/viewprofilepage/user-id/5437012) : contributors can create ideas, but you should think of it more like a "submission form" - they can submit it, not edit it after the fact.

It's a bit wonky, we're discussing where we take it next.

In the meantime, I can see 2 options:

* If these contributors have a Jira license (any Jira, doesn't have to be Jira Product Discovery) - then you can ask them questions via comments (you mention them in the comments with your question, they receive a notification, they can reply back and you'll be notified)
* If they don't, then you can't assign ideas to them and they won't receive notifications when mentioned in comments. But you can create an automation rule that sends them a notification/email when you need more info (for example after moving the idea to a "needs more info" status, or based on a field value)

An alternative we recommend for scenarios like this is to separate your product discovery project from the process where people can make requests. That's what we use in our team.

* We have a Jira Service Management form/queue where people can ask things or send feedback
* We have a Jira Product Discovery project with all our product ideas and roadmaps
* When someone requests something, it lands as a ticket in the JSM queue, we look at it, we ask questions to the requestor by replying to the JSM ticket, then if we want to action it we add it as an insight to the idea (using the Chrome extension)

This provides a clean separation between what people ask for, and the place where we have all product discussions. Otherwise if we let people create ideas in our product discovery project directly, it would become a mess really quickly.

comments: author: Hariharan Y
body: They don't have JIRA Licenses as they are not part of Product/Engg. I have added them to the contributors group for the Product discovery module in JIRA. I do not require them to Edit an idea after submission, but would just want to assign it back to them so they can provide their comments as responses to our questions.


Tags: cloud

jira

jira-product-discovery

jira-software-cloud
?annot start the free version of the Product Discovery - technical trouble
Asked by Nick:

Dear Product Discovery Support!

Can you please help activate the free version of JPD, since we cannot do this due to technical trouble.

The problem was previously encountered on the forum.

Thanks in advance!  

![Screenshot_29.png](https://community.atlassian.com/t5/image/serverpage/image-id/313839iD5489A2DBCE8B5B0/image-size/large?v=v2&px=999 "Screenshot_29.png")


Answers:
author: ManuR
body: Hello [@User](/t5/user/viewprofilepage/user-id/5003794)

We just created a new support ticket for you so we can have a closer look at what's happening on your site.

We'll be in contact shortly on ([JST-982675](https://support.atlassian.com/requests/JST-982675)) :)

Cheers,   
Manu \| The Jira Product Discovery Team

comments: author: Nick
body: Hello [@ManuR](/t5/user/viewprofilepage/user-id/1041633)

Many thanks!


author: Rohan Swami
body: [@User](/t5/user/viewprofilepage/user-id/5003794) Our support team will be in touch shortly so that we can troubleshoot this issue. Sorry for the inconvenience!

comments: author: Nick
body: Hello [@Rohan Swami](/t5/user/viewprofilepage/user-id/2842658)

No problem for sure, thank you!


author: Ste Wright
body: Hi [@User](/t5/user/viewprofilepage/user-id/5003794)

These errors can sometimes occur due to browser extensions.

Have you tried...

* Using Incognito mode?
* Using a different browser - eg. if using Chrome, try Firefox?
* Using a different device?

Ste

comments: author: Nick
body: Hi [@Ste Wright](/t5/user/viewprofilepage/user-id/1166470)

Unfortunately, these options don't help:(


Tags: free

jira-product-discovery

trouble

zzz
Automating Epic Creation Issue When Idea Status Changes
Asked by Furkan Akduman:

I would like to set up an automation where changing the status of an idea in the Product Roadmap project triggers the automatic creation of a delivery ticket (Epic) for me. I've managed to create an Epic when the status changes, but it doesn't appear under the 'Deliver' tab, nor does it show the link in the Idea details. How can I configure this automation properly?


Answers:
author: Tanguy Crusson
body: answered here: <https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Automating-Epic-Creation-Issue-When-Idea-Status-Changes/qaq-p/2647984>

comments: author: Furkan Akduman
body: Thanks


Tags: jira

jira-product-discovery
Two automations not working together
Asked by Adrian_Lester:

I've been setting up some automations as per the guide [here](https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Product-demo-Automation-for-Delivery/ba-p/2057152). Specifically, I've an automation to Transition an Idea to Done when the Epic is Done (when the Idea is linked to 1 Epic) and also Transition an Epic to Done when all linked issues are done.

Today when a dev finished the last task in an epic and moved the task to Done, one of the automations fired ok - the Epic transitioned to Done because all its linked issues are done.

However the Idea was not transitioned to Done and the audit log shows the automation didn't even fire.  

Any thoughts on what's wrong with my automation rules?  

![Transition-Idea-When-Epic-Is-Done.png](https://community.atlassian.com/t5/image/serverpage/image-id/313585i507E3837D7D94EAE/image-size/large?v=v2&px=999 "Transition-Idea-When-Epic-Is-Done.png")![Transition-Epic-To-Done.png](https://community.atlassian.com/t5/image/serverpage/image-id/313586iFD4F3BB19ABB6E35/image-size/large?v=v2&px=999 "Transition-Epic-To-Done.png")


Answers:
author: Ste Wright
body: Hi [@Adrian_Lester](/t5/user/viewprofilepage/user-id/5281113)

The second rule (which can be executed by the first) needs to be allowed to do so. This doesn't happen by default. To do this...

* Open *Rule details*
* Ensure this checkbox is checked/TRUE...
  * Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule.

\^ Let us know if this fixes the issue :)

Ste

comments: author: Adrian_Lester
body: Hi Steve,

Yes, this worked perfectly. Thank you!


author: Mart Postma
body: Hi [@Adrian_Lester](/t5/user/viewprofilepage/user-id/5281113) ,

Could you please share the details of both your audit log and the "Then: Edit issue fields - Stage, Roadmap" rule details in your first screenshot? That will help us better understand the configuration of your automation rule and identify where the issue may be.

Thanks!


Tags: automation
How do I move a project created in Jira Product Discovery from the beta/free version to Premium?
Asked by Troy Conroy:

We setup a project and configured our information in the beta/free version and then received approval to purchase and receive a Premium license for Jira Software and Jira Product Discovery. Not wanting to lose all of our work, how do we move the project from beta/free to Premium license.


Answers:
author: Tanguy Crusson
body: Hi [@Troy Conroy](/t5/user/viewprofilepage/user-id/5458110) - Jira Product Discovery doesn't have a premium plan yet (just free and standard) but if you move to the standard edition it's going to have no impact to your data. Everything will just keep working as expected. (assuming you're doing this on the same site - xyz.atlassian.net - where you used the beta/free version)

comments: author: Tanguy Crusson
body: All you need is for an admin to change the plan in admin.atlassian.net


Tags: cloud

jira

jira-cloud
Marketplace apps for JPD - timeline or roadmap?
Asked by James Conway:

Is there any timeline on when marketplace apps will be able to support or be developed for Jira Product Discovery?

I can already think of a few interesting app ideas for extending JPD.


Answers:
author: Tanguy Crusson
body: Hi James, it's not on the short term roadmap yet, but we'd love to hear what you have in mind :)


author: Sebastian Krzewi?ski
body: Hi [@James Conway](/t5/user/viewprofilepage/user-id/5356179)

Here you can find roadmap - [https://www.atlassian.com/roadmap/cloud?selectedProduct=jpd\&](https://www.atlassian.com/roadmap/cloud?selectedProduct=jpd&)

comments: author: James Conway
body: Thanks [@Sebastian Krzewi?ski](/t5/user/viewprofilepage/user-id/1561725)

So I understand from that currently there are no plans to enable marketplace apps to support JPD on the public roadmap.

That's a shame!