I need to create an acceptance criteria field in my user story form. I am using jira software cloud based.
Community moderators have prevented the ability to post new answers.
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)
Ste
I am using next-gen but for some reason the i can not see this "Create a new "Paragraph" custom field from the right-hand "Create a Field" menu by clicking on it" i do not have this menu.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That is a Classic Project - you can see this under the Project's name on the left-hand side.
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, i used Next-Gen project and everything works very well, thank you
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
thanks, it works
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
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.