-
Suggestion
-
Resolution: Unresolved
-
None
-
2
-
3
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Hi everyone,
Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use JIRA so we can continue improving your experience. We have reviewed this issue over the last few days.
The Field Required Validator for workflow transitions has been incorporated into Jira Cloud as a native feature. For JIRA Cloud customers, we recommend using this validator as the most direct way to resolve this use case.
For Jira Server/Data Center customers, the validator is only available by installing the JIRA Suite Utilities plugin, which is a paid add-on on the Atlassian Marketplace.
Please don't hesitate to contact me if you have any questions or feedback.
Regards,
Dave Meyer
dmeyer@atlassian.com
Product Manager, JIRA Platform
Original request description:
The reporter can not add an issue when he has no resolve permissions and the "fixed Version" field is a required field.
As a JIRA Administrator I want a "Fixed version" to be a required field when resolving. But it seems illogical that someone reporting an issue should enter the field. This applies to other fields as well.
Workaround
The JIRA Suite Utilities provides a fields required validator that can be configured to set fields required on specific transitions.
- is cloned from
-
JRASERVER-5783 Make field required only for one state transition
- Closed
- is duplicated by
-
JRASERVER-10847 Fields marked required are required on screens that don't provide them
- Closed
-
JRASERVER-15956 Resolution field needs to be required
- Closed
-
JRASERVER-15977 CLONE -Resolution field needs to be required
- Closed
-
JRASERVER-19183 some required fields should only be required for specific screens
- Closed
-
JRASERVER-6549 Allow to make fields required on per screen/workflow step basis
- Closed
-
JRASERVER-13668 Would like to be able to mark certain fields required on SOME screens, not all screens
- Closed
-
JRASERVER-14572 Cannot make Original Estimate Field required
- Closed
-
JRASERVER-20145 Required Fields on Workflow-transition
- Closed
-
JRASERVER-28199 Mandatory Field only on specific status values
- Closed
-
JRASERVER-45618 Allow no or null values in radio buttons & single select fields
- Closed
- is related to
-
JRASERVER-9844 Validators silently break Bulk Transition
- Closed
-
JRASERVER-9931 Failing validators during bulk transition cause index to be updated incorrectly
- Closed
-
JRASERVER-11125 JIRA 4.0 Enterprise Requirements
- Closed
-
JRASERVER-13667 Make field required per issue status
- Closed
-
JRASERVER-12773 Provide a custom field required without a "none" option on the resolve screen
- Gathering Interest
- relates to
-
JRASERVER-8100 Exception thrown by validate() method of custom Validator handled as a server error
- Closed
-
JRASERVER-15335 Remote API Interface doesn't enforce Resolution Setting
- Closed
-
JRACLOUD-5783 Make field required only for one state transition
- Closed
-
JRASERVER-2372 It would be nice to have an option to hide fields in 'Create issue' phase
- Closed
-
JRASERVER-3417 Hiding issue fields for some users /user groups
- Closed
-
JRASERVER-9088 Create a workflow validator to require a field on workflow transition
- Closed
- was cloned as
-
JSWCLOUD-24173 Make field required only for one state transition
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Wiki Page Loading...
-
Wiki Page Loading...
-
Wiki Page Loading...