Product Discovery & Custom Fields (default value)

[Ashleigh Lodge]

We're exploring Product Discovery to replace a similar tool and are really excited about the features and functionality that currently exist. The lack of a way to collect ideas is a bit of a drawback compared to our previous tool, but we can deal with a manual process for now. 

However I'm running into an issue where creating an idea doesn't automatically set the value of an associated custom field to the specified default value.

Our custom field is a multi-select list of our clients and the default value is "No Client", which works as expected for all our Jira Software projects - if no value is provided when an issue is created, the default value is selected. I associated the field w/ our Discovery project, it's available to me as a field in the settings and can be displayed on views, but creating a new idea from either the Create button in the header, or from the Create an idea button above a grid does not set this field at all - it's empty/null.

With needing to do manual data entry for ideas we were hoping that most of our internal users could be contributors with the ability to create ideas, but since I can't add this custom field to the create modal, and with Discovery and/or the field not respecting the rules for default values we're either going to have a number of (paid) creators, or leave the editing and updating of all entered ideas up to one person, neither of which is an ideal situation.

I'm open to any tips or tricks to get around this limitation and look forward to an email integration for creating ideas (our previous solution).

[Hermance NDounga]

Hello 

Default values are not yet recognized by Jira Product Discovery, but that's an improvement that we have in the backlog.

Why can't you add this field to the create modal?

Worst case that's a value you can set via automation. 

Best Regards,
Hermance
Product Manager @ Jira Product Discovery

[Ashleigh Lodge]

Thanks for letting me know that the default values are on the to do list! Automation could be a solid temporary solution, I'll have to take a look (we're not very familiar w/ Jira automation yet).

I'm not seeing any options to add fields to the create modal within Discovery (Project Settings, Features, Create ideas), is there somewhere else to do it that I'm not seeing?

@Hermance NDounga 

[Ashleigh Lodge]

@Hermance NDounga 

I just tried to set up an automation as you suggested and it's failing. Again, I don't know a lot about Jira automation, but the error I'm getting seems to suggest that it's not able to find the custom field, but it is associated w/ the Discovery project.

Do you have any additional information or suggestions?

Automation config:

Automation audit log:

I tried to test it in another project, but since the default value is respected in non-Discovery projects the rule I created wouldn't trigger.

[Ashleigh Lodge]

@Hermance NDounga

We're looking to go live in the next week or so and this gap in Product Discovery is throwing a big wrench into our process. If you have any additional information about using an automation to set the default value, or could even confirm that it's a known bug, that would be very helpful.

[Hermance NDounga]

Hi Ashleigh, 

To add fields to the create modal, you can go in Project settings > Feature > Create ideas. Then pick a view that has the fields you need. 

I'd suggest checking our product documentation for more details: https://support.atlassian.com/jira-product-discovery/docs/create-ideas-from-the-create-blue-button/

To test you automation, Make sure you are giving a unique name to your field, maybe this client field comes from another project so inside the TPD project, make sure the field is called Client_TPD, build your rule, and then rename it. 

Also I see you changed the rule config at 01:37:26 and tested the rule just 20 seconds later maybe wait a minute or two to make sure your changes are propagated. 

Best Regards,
Hermance
Product Manager @ Jira Product Discovery

[Ashleigh Lodge]

@Hermance NDounga 

Thanks for the response. I'll see if we can use a view to show the Client field, although it's the only other field we want to add to the screen, so that's a bit awkward.

Client is a global field, available in all our Jira Software and Product Discovery projects, so I'm not sure how to give it a custom name. In the Fields area of the Project Settings the name is greyed out since it's globally defined (I assume).

[Hermance NDounga]

Oh then your Jira admin would be able to edit the name, in "Custom fields" - but don't do this, this might have too much impact if it's used widely across your company.

Please open a support ticket by clicking on the "Give feedback" button on the back of the left panel, and then select support team. Include the project name, field name, rule name etc.. our support engineer will troubleshoot it for you. 

[Markus Zeppenfeld]

Hi all,

I am facing the exact same issues here. Wanted to find a solution for a default value and tried an automation which keeps failing on me the exact same way as for Ashleigh.

Did you find any solution in the meantime?

What I have tried:

• using idea creation as a trigger
• using a delay to ensure the issue has been created for good
• using assignment as a trigger (while the issue already exists)
• using default and custom fields
• renaming the fields to ensure the right one is selected
• using JSON scripts to assign the field by its ID

All of the above attempts failed with the same reason "Fields ignored".

I appreciate any idea to get this going.

Thanks
Markus

[Ashleigh Lodge]

I don't think I can be of much help Markus, sorry. We ended up creating a view in Discovery that's just used for creating issues and we put the Client field on that view and made all the fields required. 

(Discovery project settings --> Features --> Create ideas --> Select a view --> pick the template view you've already created in the project (ours is cleverly named DO NOT EDIT TEMPLATE and hidden by default + at the end of the list) and toggle the Make all fields mandatory switch on.)

Up until last week we had no Discovery automations at all, I haven't been able to get a single one to work the way I wanted to and we just found ways around the limitations. Last week I contacted Discovery support to assist with syncing a value from Discovery over to a regular Jira project and they were very helpful, which might be an avenue for you.