Hi,
i'm looking into this new JIRA agility board and can't find anywhere I can make some of the fields mandatory
Is there a specific way I need to do this on next gen projects?
Thanks
Ravi
Hi @Ravi Mistry,
Unfortunately this is not possible yet. As many thing currently this is on Atlassian Roadmap...
"Required fields, default values and more custom field types and options coming soon."
When this could be live? No idea. That is not an official information yet.
Hi Mirek and Ravi, please follow the roadmap page for updates: https://www.atlassian.com/roadmap/jira-software
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Anybody know the status for required fields?
@Pavel V, yes we are very aware of the roadmap page but what was once updated with "Shipped" items almost weekly or biweekly, now has zero updates for exactly 3 months. Has JIRA Next-Gen reduced in priority for Atlassian as a whole?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Tom Leser apologies regarding the roadmap. This has slipped through the gaps for a while - I'm currently compiling all the updates and I will publish a new roadmap next week.
With regards to required fields, a change in priorities means this will be removed from shipping soon and falls back into the backlog of changes for next-gen projects.
Again apologies for the inconvenience this will cause.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can we vote to raise priority or something?
Really miss this in nex-gen projects.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is over a year! This is a public company! OMG! wow
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello! 2020 arrived and a pretty basic functionality such as mandatory fields is not there yet. Bump for this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As everyone else is saying, when can we expect this basic feature to be available? It's like selling an expensive car without windshield wipers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nov. 2018 - first comment.
Jan. 2020 - still no update. I DO NOT want to go through a migration back to classic just to have basic functionality.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hmmm, ther is a lot i like about next gen projects, but some things i expected to be available are not. bummer... considering migrating back
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If anyone here is interested in making fields required in next gen projects, I would vote up JSWCLOUD-17631 (which I just did).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nov. 2018 - first comment.
Jan. 2020 - still no update.
Feb. 2021 - still no update.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@hullen - typical JIRA - Nothing ever gets done.
I wonder if the JIRA team uses a broken JIRA how could we expect anything more?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Almost 4 years and this basic requirement isn't available in NextGen.
If Atlassian was a new company and they released NextGen as a product it would fall flat on its face. It's an incomplete offering.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Ravi Mistry - it's not possible to have a mandatory field on issue creation in next-gen projects; however it is possible to create a workflow rule to check a field has been populated on transition to another status "Check an issue's field" https://confluence.atlassian.com/jirasoftwarecloud/add-or-remove-workflow-rules-in-next-gen-projects-1005805110.html#:~:text=Rules%20help%20you%20streamline%20your,workflows%20in%20next%2Dgen%20projects.
For mandatory fields on issue creation, you can add your vote to the feature suggestion here https://jira.atlassian.com/browse/JSWCLOUD-17631 This will happen, although not likely in the next 12 months.
Apologies for the inconvenience!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This rule doesn't work for us. Should it stop the transition from happening if the rule isn't fulfilled?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@matt.belway it should prevent the transition happening. Can you share a screenshot of your rule and explain what it is you are trying to do?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I suffered this issue for a while. With the recent automation feature, I had the following workaround solution as the site admin.
Trigger: when a new task is created and required custom field is not filled.
Action: Send the initiator an email cc to me telling the required field is blank.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You still let the task to be created with the blank "mandatory" field. If you have standard jira this automation could easily use up the 1000 max usage per month.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm new at Jira, at work before we suppose to use our developed product. But from now on what I see, is Jira need to make money on APP so they get rid of basic functionality and literally force companies to use external JIRA APP.
It is a big shame.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@[deleted] - doesn't seem so. I'd vote up JSWCLOUD-17631 if you're interested in being able to set fields as required in next gen projects.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.