Are there list of insights view somewhere?

[Oriol Fàbregas Pujol]

Hi
I normally use and like these levels:

- Insight

- Problem/opportunity (normally a pain, job or gain)

- Solution

Insights come from customer interviews, market research or competitors analysis and feed opportunities. (productboard does also differentiate like this)

I know you are working on a way to better distinguish problems from solutions inputs so that they can be visualised more easily from a tree.

However, my questions are:

1. Are there ways to register new insights from outside the main idea object so that you don't necessarily link an insight to a particular opportunity from the beginning but maybe later?

2. Thus, is there a way to visualise insights in a list? 

[Erin Quick-Laughlin · Accepted solution]

I believe it's because of the quotes surrounding the object that contains start and end props.

When I post your code into jsonlint.com, it shows this:

After I took those out, it also threw errors on the escapes, so try this?

{
  "fields": {
    "customfield_10552": {
      "start":"{{now.JiraDate}}",
      "end":"{{now.Jiradate}}"
    }
  }
}

BTW what kind of custom field type is this?

[Martin]

Thank you Erin. I'm bookmarking this tool.

It's a date field in JDP. 

I used the exemple provided by @Hermance NDounga in her documentation. Copy/Paste and changed the field number only.

[Martin]

I asked also a new friend, that sometimes, knows a lot. His name is chatGPT. It gave me the right formula and it works:

In your JSON, there is a small issue with the casing of the jiraDate placeholder. In Jira Automation, the correct casing for the current date placeholder is {{now.JiraDate}} with an uppercase "J" and "D".

Here's the corrected JSON:

{
"fields": {
"customfield_10552": "{\"start\":\"{{now.JiraDate}}\",\"end\":\"{{now.JiraDate}}\"}"
}
}

This JSON assigns the current Jira date to both the start and end properties within the customfield_10552 field.

[Chris Timms]

Commenting to track if anyone comes up with a solution to this one. My own investigation suggests it might be related to escaping special characters correctly, bbut I haven't been able to invest the time to look into it deeply.

Regards,

-C