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)
@vicky Required fields are coming soon
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
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.
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.
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!
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
For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events