Custom Formula's unsupported in published views - Workaround?

[duncan.crowell]

I found out the hard way around unsupported fields when publishing views that is well documented at https://confluence.atlassian.com/jpdkb/error-when-trying-to-publish-a-view-in-jira-product-discovery-1346052400.html.

I have found the custom formula one in particular to be a big limitation when trying to communicate priority to stakeholders using a RICE or DVF model. Whilst I have been able to create visibility of the scoring the most important element which stakeholders are asking for (the priority score itself) cannot be published.

• Question to the JPD team - Is Custom formula visibility in published views something that is coming? if so, any view on when?
• Question to the group - How have others worked around this limitation without literally manually updating a duplicate number only custom field?

[Melorie Acevedo]

I have the same problem and have not found a workaround.  Any information would be greatly appreciated. 

[Jeroen Rommelaars]

I would like to voice that this could also be a very valuable feature for usage on my end. Setting up custom formulas have a reason - and I would like to be able to share these formulas, which currently cannot be done.

[Mike Chien]

+1 Also have not found a workaround for this besides giving those stakeholders a Jira Product Discovery account which I would rather not do.

Having the final score and in rank order would make the Publish view so much more valuable. 

[Melorie Acevedo]

Hello, I agree. This is a problem we are also struggling with.  I tried to create a numeric field and copy our formula into the numeric field, but this was too labor-intensive.  Suggestions are appreciated as we grow in our JPD usage and adoption.

[Josh White]

This is also a big issue for us... we have a Custom Formula that does some maths on our scoring for Reach, Impact and Effort (and a little from the number of insights) and this calculated "Weighted Priority Score" is what drives the ranked list of value opportunities.

We want to be able to share the ranked list of value opportunities with our stakeholders... but it is not possible!