youngmon/atlassian-qna huggingface dataset:
Product of Products approaches?
Asked by George Moberly:

We are evaluating JPD now. Our Jira dev projects are broken into a project per product (roughly) - and we thought to have a JPD project her dev project for symmetry.

Question is, if Ideas span multiple products (probably in our case maybe 20% would) does it make sense to have a separate project for "Initiatives"? What are best practices for having a layer "above" product ideas?


Answers:
author: Tanguy Crusson
body: Hi George, you have 2 ways to think about it:

1. You could create a single JPD project for all products, and create different sections with views for different teams and products. That way an idea can appear in different products and teams views. We have customers who have 250 people working in the same project. If it's set up well and people understand how to participate in the project, it can work pretty well.
2. You could create different projects, but then it isn't possible to have an idea belong to different projects. However, you could indeed create a separate project for your initiative-level ideas and link these to ideas in each team's project. You just wouldn't be able to visualize these relationships in views (initiative - team idea). That being said, we're currently working on features that will eventually make that easier.


author: Denis Paul
body: [@georg](/t5/user/viewprofilepage/user-id/633635) I like to use Plans (Ex Advanced Roadmaps) for cross team planning. You could use the new integration with JPD if you have that included in your Jira license: <https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Early-Access-Program-new-integration-with-Jira-Plans-ex-Advanced/ba-p/2743110>
Jira Product Discovery Backups
Asked by Robby Keefer:

I want to understand if the Backup for Cloud backup job includes Jira Product Discovery content (Ideas, Idea Attachments, Delivery References, Insights, etc).

There is conflicting information in the community which makes it unclear if JPD Backup support currently exists.


Answers:
author: Hermance NDounga
body: Hi Robby,

The backup will include everything except:

* Insights
* Views

For views, each project will get a list view, and you'll need to re-create them. For insights, unfortunately, you would need to recreate them manually, and there is no workaround. We are aware this situation isn't ideal and we are working with the team in charge of the backup functionality to include insights in the future.

Cheers,

Hermance


author: Tanguy Crusson
body: Hi [@Robby Keefer](/t5/user/viewprofilepage/user-id/1216949) : [@Hermance NDounga](/t5/user/viewprofilepage/user-id/430755) (our resident expert for this) is currently away but will reply as soon as she's back.
Atlas Not Appearing as a Date Source Option
Asked by Jess Wong:

I have the Atlas integration enabled for my JPD and have been able to successfully link to Atlas Projects and Goals, however, when I try to configure Start or Target Date fields to auto-populate from Atlas, I only have the option to link to Delivery tickets.

I've tried logging in and out, refreshing, and even removing all delivery links to see if it'll trigger the option with no success

![Screenshot 2024-07-15 at 3.28.00?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/335757i1785FDB3CC1F3BED/image-size/large?v=v2&px=999 "Screenshot 2024-07-15 at 3.28.00?PM.png")


Answers:
author: Tanguy Crusson
body: [@Jess Wong](/t5/user/viewprofilepage/user-id/5544508) We found what your issue is (thank you for reporting it!). There's something we forgot to turn on when rolling this out to everyone. We'll fix that soon.

comments: author: Tanguy Crusson
body: Edit: it's done - if you refresh your screen you should see this option now [@Jess Wong](/t5/user/viewprofilepage/user-id/5544508)


author: Jess Wong
body: I see it - thank you for the quick fix!


Tags: atlas
Send an email with multiple ideas after variable creation and compare in automation
Asked by Sahar Qarem:

Hello,

I've created the automation in the screenshot, based on the feedback [Here](https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Automation-creation-for-quot-Project-Start-Target-quot-custom/qaq-p/2750068?utm_source=atlcomm&utm_medium=email&utm_campaign=solution_to_question&utm_content=topic).

The intention is to notify once an idea has a project target due in the next 7 days. And it works but sends an email per result

I'd like for all these issues (ideas) sent be in one email instead of an email per issue.

I've tried using lookupissues after variable creation but it didn't work.

Any thoughts how to make it work?![Screenshot 2024-07-15 at 09.46.53.png](/t5/image/serverpage/image-id/335554i4A72AF5404D0CF1B/image-size/large?v=v2&px=999 "Screenshot 2024-07-15 at 09.46.53.png")


Answers:
author: Nick H
body: Hi Community,

Reposting here as well for visibility - we were able to get this resolved through a support ticket using an automation like the one below - which can send a daily email of all ideas if their JPD date-field matches the present day:

![sched1.jpeg](https://community.atlassian.com/t5/image/serverpage/image-id/337337i666565AC5E0FD998/image-size/large?v=v2&px=999 "sched1.jpeg")

1) WHEN: Select schedule for automation to run

2) THEN: Lookup issues - JQL:

```
project = XYZ AND cf[00000] ~ "\"end\":\"{{now.jiraDate}}\""
```

\^ cf\[00000\] is the JPD date-field's ID. Can find this using this doc:

* [How to find any custom field's IDs](https://confluence.atlassian.com/jirakb/how-to-find-any-custom-field-s-ids-744522503.html)

3) AND THEN: Send email - which uses the [Lookup issues](https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues) from previous step to list all ideas in email body using this:
>
> ```
> {{#lookupIssues}}* {{key}}, {{summary}} - {{url}}{{/}}
> ```


author: Nick H
body: Hi [@Sahar Qarem](/t5/user/viewprofilepage/user-id/5308011) ,

I had shared a suggestion in that other Community questions.

It might be worth opening a ticket with [JPD support](https://support.atlassian.com/contact/#/) to further troubleshoot this issue, especially if customfield_10152 is not returning anything when adding it as a Log action to the automation.

You should also be able to enter a ticket with them directly in your JPD instance under the *Give feedback* tab \>\> *Get help from the support team*
Private view in jira product discovery
Asked by Andrew McLoughlin:

I want to set up a view in Jira product discovery that can only be accessed by certain people who are all creators in the jira product discovery space. I would also like this view to be permission based so if people want to look at it they will need permission. Is there a way in JPD to set up a "private view"


Answers:
author: Tanguy Crusson
body: Hi there, not yet but it's something we're working on. It will be a feature part of the JPD Premium plan. You can join the waitlist to get early access here: <https://www.atlassian.com/software/jira/product-discovery/premium>


Tags: cloud

jira-product-discovery
Im new on the scene
Asked by Ronald Wessels:

I\`m new on the scene and need to know what the atlassian community is all about. Im from Cape Town South Africa.


Answers:
author: Nicolas Grossi
body: [@Ronald Wessels](/t5/user/viewprofilepage/user-id/5543206) WElcome Community is here to help you on any issue regarding the whole Atlassian's suite of applications.

Regads

Nicolas
How can I make the Atlas Date work for Published Views?
Asked by John McDonald:

We use JPD for all of our product planning and roadmapping, and I've been creating published views for stakeholders. We use the Atlas Date field as the Target Date for our projects, but it looks like that view does not come through for Timeline views, or any views for that matter. Ummm, what? This is a major issue for us as we basically cannot provide accurate views for stakeholders. Is there a workaround that doesn't involve us having to manually update a secondary date field specific to publish views? (This is a pretty big deal for us, and we are a major enterprise customer of Atlassian)


Answers:
author: Tanguy Crusson
body: [@John McDonald](/t5/user/viewprofilepage/user-id/5018829) that's an oversight on our part: the Atlas project field is not yet supported in published views, so you shouldn't have been able to publish this view in the first place. We'll start by fixing that.

We'll add support for Atlas project fields in a subsequent change.

Thank you for reporting this!

comments: author: John McDonald
body: Thanks Tanguy - I appreciate the response. I'm curious if you have any estimate for when you think Atlas fields will be supported in published views? This will help determine what changes we make to our published views in the interim. Thanks!


author: John McDonald
body: [@Tanguy Crusson](/t5/user/viewprofilepage/user-id/502312) Just circling back on this - do you have any recommendations for how to manage published roadmaps, when we are heavily leveraging Atlas for the management of the Target Dates? Is the solution to manually duplicate the Atlas Target Date into a field that the Timeline View will accept in the meantime?
Story points for Discovery itself?
Asked by Michael Seguin:

I know that we can track velocity issue delivery issue count or by aggregating delivery ticket story points - but does anyone have a process in place to track story points for the process of discovery itself?   
We could certainly create a delivery Jira ticket for discovery, and assign story points to that delivery epic, but that seems reundant?


Answers:
author: Dirk Lachowski
body: Like this? <https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Resource-planning-with-JPD/qaq-p/2750394>
How to group statuses without automation (i.e. sync an attribute to status) - custom formula?
Asked by Bryce York:

We're in need of a grouping mechanism to act as an abstraction of Status since we've implemented a large number of statuses so that stakeholders can know at a glance what the status of the Idea is.

We have 4 "stages" that logically group our \~25 statuses.

To prevent data entry errors and allow users to only have to worry about keeping status up-to-date, we need the Stage to be automatically sync'd with the Status.

This is of course possible with automations, but it's impractical with the 1000 runs per month limit.

I'm really hoping we can use a custom formula or something else instead... Any ideas?

Here's an extract of our workflow chart for reference (the black boxes are Stages and the gray are to-do Statuses):

![Screenshot 2024-07-12 at 09.50.17.png](https://community.atlassian.com/t5/image/serverpage/image-id/335294i02BCFE9A6AAD45FE/image-size/large?v=v2&px=999 "Screenshot 2024-07-12 at 09.50.17.png")


Answers:
author: Amina Bouabdallah
body: Hi there! To auto-populate the Stage field according to the Status field, the only available solution today is automation. It's the only place where you can run IF-like operations to create field values in JPD!

comments: author: Bryce York
body: Thanks for clarifying. That's pretty disappointing given the extremely low limits applied. It's honestly outrageous to have such low limits.
Creating costume formula in Product discovery
Asked by Raj Agarwal:

Hello,   

I've been exploring JPD for product roadmap and prioritisation and wanted to know if it's possible to create custom formulas using IF AND conditionals as I need to assign weights to items based on certain parameters which would be their own columns in the template.


Answers:
author: Amina Bouabdallah
body: Hi there! today, formulas cannot be built using conditional operators today. What you have available is mathematical operators: add, substract, divide, multiply.

We'll take a note of your need to have conditional operators for formulas.

Thank you!

the JPD team
Resource planning with JPD
Asked by Mark Colonnese:

Hi,

We are in the process of refining our roadmap across various impacted teams. We create ideas in JPD and assign teams to those ideas. Each team then sizes their t-shirt effort to that initiative.

We wish now to check we have the capacity within each team to deliver our roadmap commitments over a defined timeframe.

Does anyone have a solution for this?

Thanks!  
Mark.


Answers:
author: Joni Johnson
body: Not sure if this will work as I am new to JPD. If you have Plans in Jira, which is included with Premium and Enterprise Jira, you might build a plan on the ideas, associate the teams, assign each team's capacity, and set an estimating model for plans. I'm also not sure how the t-shirt sizing will translate.


author: Amina Bouabdallah
body: Hi there!

Today, after you add your ideas in JPD, and build your roadmap using JPD views, you can link delivery tickets that exist in Jira to the right ideas. Then for each idea, you can follow the delivery progress for every idea.

To understand how much capacity is available, and what piece of your aspirational roadmap you can commit to: we don't have a built-in feature. You would need to compute this in Jira, using Jira tickets, then doing sequencing in Jira, then reporting manually the right dates on ideas.

This is a great use case though!! I will circle back with the team to see if they have a better solution in mind.

Thank you

Amina


author: Amay Purohit_RVS
body: Hi [@Mark Colonnese](/t5/user/viewprofilepage/user-id/5487995)

Welcome to the community !!

A mktplace app can help to plan the capacity of your teams. If you are open to try one, take a look at :

[Capacity Planner](https://marketplace.atlassian.com/apps/1231411/capacity-planner?hosting=cloud&tab=overview%20)

With the add-on you can :

* Maintain the team members daily capacity in a template and decide work allocation.
* Define resource leaves.
* Plan capacity either for time estimates or story points.
* Check the effort progress of the resource and make decisions accordingly.
* Track the actual time spent per task

Do try it out.

Disclaimer : I work for the vendor who built this app

![Work Distribution.jpeg](https://community.atlassian.com/t5/image/serverpage/image-id/334871i5FD86A009256EDF3/image-size/large?v=v2&px=999 "Work Distribution.jpeg")

![Resource Tasks.jpeg](https://community.atlassian.com/t5/image/serverpage/image-id/334872i37CE819AEBAD8697/image-size/large?v=v2&px=999 "Resource Tasks.jpeg")


Tags: resource-plan
Salesforce integration non-numeric fields
Asked by George Moberly:

I saw same question but want to re-ask it, as the inability to display string fields from Salesforce in JPD views will be a major issue for us (we are evaluating Aha replacements). We represent a good size revenue opportunity so I'd like to know how we can engage Atlassian directly on this topic.


Answers:
author: Tanguy Crusson
body: Hi [@George Moberly](/t5/user/viewprofilepage/user-id/5539940) , we are not planning to change this at this stage - this request comes up very episodically (however there are others that are getting a lot of demand).
Are there any plans to embed data visualization tools, like Tableau, into Idea Descriptions?
Asked by jack_saxton:

Our team uses Tableau pretty extensively as our analytics platform for data visualization. After seeing how Google Slides so neatly embed into Idea Descriptions, I'm curious if there are plans to do something similar for popular data visualization tools?


Answers:
author: Tanguy Crusson
body: Hi [@jack_saxton](/t5/user/viewprofilepage/user-id/2318366) thanks for the feedback - we'll pass it on to the team working on "Smart Links" (when you paste a link - it transforms into a card or embed in any Atlassian product text box).
Is it possible to link tickets from a Discovery Project to Software Project.
Asked by Sian Snook:

Is it possible to link tickets from a Discovery Project to Software Project.

Currently there is a an error when I link tickets from the projects.

The current options seem to be

1. Add a comment in the software project with the ticket from Discovery Project.

Questions?

1. Could I link the tickets in the link functionality ?
2. More move the ticket from Discovery project to the Software project (link u can in software projects.


Answers:
author: Angie Adams
body: We have been able to link them together. However, the person doing the linking must have creator rights in the discovery project. Without the right permissions in the projects, the link will fail.


author: Tanguy Crusson
body: HI [@Sian Snook](/t5/user/viewprofilepage/user-id/5539817) , could you please share the error you get ?


Tags: cloud

jira-work-management

jira-work-management-cloud
Jira product discovery filter - xls export
Asked by Caroline.Muon:

When I create a filter with Jira Product Discovery, fields with formulas do not show up in my xls export.  
How do I get them into an xls export?  
Thanks


Answers:
author: Aron Gombas _Midori_
body: There is a fairly easy solution (two actually!) for this with the Better Excel Exporter app!

Options:

1. Create a new Excel template, and add your JPD formulas as [Excel formulas](https://midori-global.com/products/better-excel-exporter-for-jira/cloud/documentation/formulas) to the template. That way, every time when you export, the Excel formulas will be inserted to the exported Excel file and they will be evaluated normally. (You will basically duplicate your formulas in the template, but you only have to do this *once*!)
2. Define a [calculated field](https://midori-global.com/products/better-excel-exporter-for-jira/cloud/documentation/calculated-fields) and implement your formula in Groovy code. When the value of the field is inserted to the exported file, the Groovy formula will be evaluated, that's it. (You will basically duplicated your formulas in Groovy, but assuming that your formulas as fairly simple arithmetic, the Groovy code should be trivial.)

*(Discl. it's a paid and supported app developed by our team. Free for 10 users!)*


author: Bill Sheboy
body: Hi [@Caroline.Muon](/t5/user/viewprofilepage/user-id/5515609)

That is not possible yet. Please see this other question with the response from the JPD team:

<https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Exporting-Data-in-Jira-Product-Discovery-issues-with-Formula/qaq-p/2248594>

Kind regards,  
Bill

comments: author: Caroline.Muon
body: [@Bill Sheboy](/t5/user/viewprofilepage/user-id/1685313)

Thank you for your reply  
Hope that the formulas will soon be integrated into the exports ?


author: Amina Bouabdallah
body: Hi there!

What formulas are you using? Just tried formulas in my JPD project and did an export, I can see the values!

If you have more details, it might help to diagnose.

Thanks!

comments: author: Caroline.Muon
body: If you extract the data from the project, the formulas are included in the export, if you extract from the filters, the formulas are not included in the file.  
For my using, I need to export with filters.


Tags: cloud

jira

jira-cloud

jira-product-discovery
Multi Select Field Limit "This field has reached its maximum of 500 options."
Asked by Zach Clarke:

Hello,

Our company has added our customers to a Multi Select field as a way of associating which tickets are associated with which customers.

Each month I update the list with new customers. Today, when entering customer number 501, I ran into an alert "This field has reached its maximum of 500 options".

We've trained our users on how to select customers when creating new and editing existing tickets and team members are currently building reports off the customers listed.

Are there any options available for increasing the number of values that can be listed in a Multi Select?

If not, are there other suggestions?

Thanks!![next customer.JPG](https://community.atlassian.com/t5/image/serverpage/image-id/333749i1550F987D07B1105/image-size/large?v=v2&px=999 "next customer.JPG")


Answers:
author: Owen Friedrich
body: We had a similar need to track customers to Ideas but elected to not use a Multi-select field and instead created a Jira project of "Customers". We then link the Customer to the idea using native Jira linking. Added bonus is you can easily pull up a customer in the Customers Jira project and see all the linked ideas in one shot.

comments: author: Zach Clarke
body: Thanks for the reply, this sounds like a great option with additional benefits. I appreciate the feedback.


author: Tanguy Crusson
body: Oh wow that's pretty cool [@Owen Friedrich](/t5/user/viewprofilepage/user-id/5337556) ! I never thought of doing it like that but it makes complete sense


author: Owen Friedrich
body: Not mentioned earlier but we automatically sync the customers from Salesforce over to the Jira project using Boomi. We also just started to associate actual delivery tickets (not just JPD ideas) in Jira proper back to the customer in this project. This lets our customer success and support teams see and report on progress for items that their clients are waiting on.
Missing Date Options for linking Project Target custom field to Jira Ticket date field
Asked by duncan_crowell:

Hey Team,

The Question is hard to articulate here but hopefully with more context here someone will understand (and possibly share) my dilemma.

We are currently using Jira Align as the Program level Delivery tool and Jira Software for Team based delivery management as well as Jira Product Discovery for Pre-Delivery Idea capture and Discovery.

Something I am trying to do is align the Epic start and target dates across all 3 tools. Jira Align is currently setup to auto sync the Epic start date to a customer field called "Start Date" and the Epic end date in Jira Align is setup to sync with the Jira default field "Due Date" Per below:

![image.png](/t5/image/serverpage/image-id/333580i71B4EAB710AEB89D/image-size/large?v=v2&px=999 "image.png")

THe intent here is to Link my "Project Start" and "Project Target" fields in JPD to the Jira Field IDs so then the start and end dates are always in Sync.

Start Date is no issue as I am able to link my "Project Start" field to that

![image.png](/t5/image/serverpage/image-id/333581i5E6D255C7DF52E7C/image-dimensions/298x455?v=v2 "image.png")

However the Standard Due Date field does not seem to be an option when trying to do the same for my "Project Target" field.

Now I believe I can easily create a new custom field here but I am trying to avoid a wider spread change as Delivery teams are already used to using Due Date when making the changes within Jira Software.

Keen to hear if I am missing something here and its a simple fix, or is this a known limitation?


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

I believe the field options for the autofill toggle will show based on the **global Jira permission**.

Since "Due Date" is a system field that will show up on any Jira project, only a Jira Global admin will be able to select it for as an option / toggle for the JPD date field.

That being said, once configured and selected in the JPD date field - all users will be able to see the value on the field, so the admin only needs to select it once.

comments: author: duncan_crowell
body: Awesome thanks Nick. That explains it :)