Create a custom field with choices and choices for criteria and update the workflow with the parameters to meet that criteria before progressing in workflow.
If you want just criteria for creating the issue then take the field and make it required so that it cannot be empty upon issue update (or creation). The tricky part is to ensure that after initially populated any changes to other parts of that issue are not blocked because the required field had not changed.
Are you looking to create a separate custom field for Acceptance Criteria?
If this is Next-Gen, this is how to do it:
If this is a Classic Project, it's considerably different. This is because Classic project custom fields are designed to be used across multiple projects so need different layers of configuration.
This is how I'd do it - but you can modify it as you see fit:
^ If you want to only have the Acceptance Criteria field on the story screen and need new screens for other issue types, you'll need to create more screens and associate them through screen schemes / issue type screen schemes to different issue types.
See this page for information on screen creation (and on the right-hand menu how to associate these with schemes)
When to use CSV importer When managing your processes in Jira, there are many occasions where you need to create a lot of tasks. Creating them one by one will cost you a lot of time and effort and i...
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