JSM <> JPD - Configuring Properties on Insights

[trevor.devroome]

Background

I'm using JSM as our intake form for feedback, in which I've added a number of custom fields to collect specific information I want (eg. categories, segments etc.)

I'm then using the JSM <> JPD integration using the Chrome extension to pass feedback between the two - as shown in this video:

https://www.loom.com/share/45f1cdd114ce4f9393d9272bd5053189

In this - I'm trying to configure the insights (so JPD ticket > Insights > configure > Configure Properties screen) - but can't see some of the fields I added to the JSM form that I'd like to pass over (eg. categories, segments etc.)

Question

How (or is it even possible to...) do I configure what is shown in the configure properties screen for insights from JSM <> JPD?

[Pieter Helsen]

Hi,

This isn't necessarily a Product Discovery question, but I'll try to answer. 

There are two ways of making fields mandatory:

• As part of a validator during a workflow transition (i.e. from To Do to In Progress)
• As a mandatory field (upon creation)

It looks to me you would like to do the second, but unfortunately, that is not possible for the Parent field specifically. The workaround is to change your workflow and add a validator on the Create transition that checks if the field is empty.

More information is available here: Configure advanced issue workflows | Atlassian Support

[Christopher Maxwell]

Hi @Himani ,

Peter has some good info. And yes, this sounds like a Jira question (not Jira Product Discovery).

I would add that in a team managed project, you'll want to make sure the field for the epic name is active, and in a Team Managed Project, the field is titled "parent name" in the field chooser.

Also, you can utilize Automation to send a notification if an issue is created with a blank epic. This, combined with some team education, is another route to take.

[Himani]

@Ashish