nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Required fields in next-gen projects?

vicky_1qi1zu

How can I make a field required in a next-gen project?

Also how can I remove standard Jira-created fields from next-gen projects (for example - linked issues)? I don't see any relationship between the next-gen project fields and the issue type screen configurations in Jira settings (I'm using both a next-gen and a classic project in one instanced)

Accepted answers

All comments

Pavan_ak86gn

@vicky Required fields are coming soon

https://www.atlassian.com/roadmap/jira-software?_ga=2.159727229.1350828060.1543266147-184170155.1539377757#result-066d462c

This Article Might help you https://community.atlassian.com/t5/Next-gen-articles/Everything-you-want-to-know-about-next-gen-projects-in-Jira/ba-p/894773

Migrate from Next project to Classic Projects https://confluence.atlassian.com/jirasoftwarecloud/migrate-from-an-next-gen-project-to-a-classic-project-957974933.html?_ga=2.229965788.1350828060.1543266147-184170155.1539377757

Joe St.Louis

I Don't see Required fields on the roadmap anymore @Pavan did this get removed?

Doug Wieand

Bump for this

m.drag

Bump for this

danny_lake

Next-gen projects shouldn't even be available for general use without this functionality.

Carlos Tolosa

Hello! 2020 arrived and a pretty basic functionality such as mandatory fields is not there yet and its not even in the roadmap. Bump for this.

Andy Heinzer

Hi everyone,

Thanks for the interest here. I unaccepted the previous answer here as it appears that this feature has not yet been implemented in next-gen project, nor is it currently on the roadmap.

I would invite everyone that comes across this thread and wants to see this feature in next-gen projects to vote on JSWCLOUD-17631. While this is not the only way we gauge interest, it can be used as a factor in helping to prioritize new features in next-gen. You can also watch that request if you want to see updates on the status of this request.

Thanks

Andy

Ralphette English

Can someone confirm if this feature is now available? I do not see it on the roadmap that was shared in Q4.

Bump on this

will vote

Bump on this

Why does Atlassian release new versions without key features

Carlos Lopez_9w4adr

Bump on this

Bartek Kobyłecki_yzp5lo

The key is what the key means depends on perspective

Luke Jones_1vn6kq

Bump on this

Akif Sayeedi

Any update on this? I would like to know if we can configure the screens on the next-gen projects.

unknown

BUMP!!!!!

Aaron Bethea_eb359i

This question just came up today in my organization. BUMP.

Nate Fanaro_qs59cq

Voted, commented, and honestly not optimistic that this will be addressed any time soon.

Robert Bowell

Honestly can't believe such a basic feature is missing from a Gartner 2020 Magic Quadrant for Enterprise Agile Planning Tool

Chris Hyde_l8pli5

Is this thing on? We need this feature...

Dave Liao

I see 31 folks (so far) have voted up this answer - you all should vote on JSWCLOUD-17631! That JAC ticket seems to be the official story for this. 👀

Dave Liao

Voted!

Steven Paterson_rp78v9

Next-Gen still does not have the required field option.

However, as a workaround for now. You can create a workflow rule not to allow stories to move from one swimlane to the next.

For example, I have a rule that says that a story cannot move from To Do -> In Development when the "Requesting Customer" dropdown is blank.

NOTE: You can add workflow rules by clicking Edit Workflow from the Issue Types editor and then creating a "Check an issue's field" for the appropriate transition.

Sarah Clements

I've just managed to ensure a field is completed before moving to a defined status by using the new workflow tool, along with automation, in a next gen board area.

There is an ellipsis in the top right, with the option to 'Manage Workflows'. This tool then allows you to create a transition, and add a rule which can make sure a field is of a specific value, or not empty

Not empty is configured by selecting 'does not contain' and leaving the options blank - this wasn't immediately obvious to me so hopefully this helps!

Sarah Clements

There are some downsides to this - as a user itsnt told why a status isn't available, it just isn't there, which isn't too helpful. However, if you set up a full workflow, the user will have no options to transition until the data is there - which i suppose is better than no data

Jadranka Perc

Thank you! I found it but when tried to restrict moving from QA to Done with Fix Version..this field is not in the dropdown option (

Lachlan Macnish

Wow that's awkward. And do we have to do this for every "Issue Type"?

A simple "Required" option when configuring the Issue Type would be nice...

Armen Babakanian

bump

Mike Grande_7r3bli

Seems like the best solution is to find another product... this is unacceptable

Bump!

bump!

This was posted in 2018, and three years later this has not been resolved. Everyone in the community has complained about this but apparently the company is only concerned about share holder interests not user interests. Definitely looking forward to switching to a better alternative.

Sam Prince_nsn9u5

"Check an issue's field" only seems to allow me to pick built-in fields, not fields I have created.

Steven Paterson_rp78v9

@Sam Prince It should work on custom fields. It is working for my custom fields.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-software

next-gen