Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Are there list of insights view somewhere?

Oriol Fàbregas Pujol
Contributor
June 28, 2022

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? 

1 answer

0 votes
Rohan Swami
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 14, 2023

Hi @Mart Postma, Components are project-scoped fields meaning that they can not be used outside the project. I'm curious though, can you tell me more about your use case? Why do you need to connect Jira Product Discovery to Components?

Mart Postma
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
September 14, 2023

Hi @Rohan Swami, thanks for your answer - and your question.

In our project, the software system that we are developing is divided into many components of which each component has fields such as assignee, linked issues, etc.

Now I want our customers (Contributors/Stakeholders) to be able to submit an idea for a specific component of our system. 

Let's take Facebook as an example. Assume that they have divided their system into Components as well, such as Main Feed, Marketplace, Comments, Events, etc. etc.

If a customer of Facebook wants to submit an idea for a specific component, then it can select that component in the Idea Template, and describe further specifications. 

With some automation rules, then for example this idea can be linked to some other issues in Jira, as well as assigned to the component owner of Facebook. This prevents product managers having to triage and assess every (new) idea thoroughly. 

Thus, I wish to achieve a similar functionality in our system, as our customers are familiar with the naming of our components in the system.

Hope it is more clear. Let me know if you need further explanations!

Like Brent Vierling likes this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events