Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Required field validator for Product discovery workflow


Is it possible to set Required field validations for Product discovery workflows as we do with JIRA?

When creating an issue I want 3 fields to be set as required fields

1 answer

1 accepted

1 vote
Answer accepted
Tanguy Crusson
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 26, 2022

Hi @serhat , it's not something that the product supports today. 

There's 2 related features though:

  • if you create a view with a filter (e.g. "product = A and team = X"), and you create an idea from that view - then these field values will be automatically applied. 
  • you can create templates for an idea's description - to standardize how ideas are defined (e.g problem definition and validation, etc.)

Thanks for the prompt response @Tanguy Crusson 

- Is this something in your roadmap?

- I find fields useful rather than raw description text since I prioritize the feature depending on the field values.

- I like your idea #1. But I want them required not optional if I understood correctly. I like to create ideas with the "Create idea" button.

Tanguy Crusson
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 27, 2022

It's not something that comes up frequently as feedback @serhat so not high priority today. Usually the teams we talked to looked for a more flexible/less structured way to capture information quickly as ideas - and refine them later if/when they decide to explore them in more details.

We definitely do plan to integrate better with the "create idea" button though, so it works the same from that dialog - but it's not there yet today

Tanguy Crusson
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 27, 2022

If you don't mind sharing: what are the fields you want to make compulsory?

product area



Like # people like this

@Tanguy Crusson I wanted to share a few more use cases as to why the required fields would be a nice enhancement. Today we use Initiatives in Jira Software for capturing all the details about the particular feature or product. This is where the Product Manager does the bulk of their work before creating Epics.  In addition to the description, we have a handful of fields that capture Impact, Effort, target release, target first sprint, stakeholder validation, etc. All initiatives go through a review process for quality and prioritization before any of the work makes it to a dev team. Having the validation rules as part of the workflow helps enforce quality of requirements and also reduces approval churn. 

Like # people like this

I have tried using automation to validate a field before entering a Product Discovery status. It is more 'clunky' than the Jira Software experience, but was possible.

Our product managers collaborate with technical teams. We would like to capture a formal approval of a requirement or design, therefore this validation would be helpful in our industry.

Any updates on this?
Or any ticket we can vote on?

This would be a good feature to add as many steps often require validation before moving forward.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events