-
Suggestion
-
Resolution: Unresolved
-
None
-
0
-
2
-
There are a number of workflow misconfigurations that can cause issues with creating and transitioning tickets. Often the UI error messages are generic or misleading. Related tickes are added to the issue links here
- relates to
-
JSWCLOUD-25852 This issue cannot be edited because of its workflow status - User is not warned when completing a sprint failed or partially succeeded
- Closed
-
JRACLOUD-81298 Date compare validator does not show the expected error time message
- Closed
-
JRACLOUD-79670 Update issue custom field post function to empty value fails for checkbox fields
- Closed
-
JRACLOUD-79736 Setting empty value on Update Issue custom field postfunction leads to Transition falied error.
- Closed
-
JRACLOUD-80310 Can't use non-existent custom field in FieldRequiredValidator validator on workflow creation
- Closed
-
JRACLOUD-81146 Field Required Validator for "Request type" does not work on issue type change even if both the issues share same workflow
- Closed
-
JRACLOUD-81545 Attempting to rename the Create transition in a workflow throws an error.
- Closed
-
JRACLOUD-81685 Invalid custom field update by post function results in misleading "Couldn't create the issue" message
- Closed
-
JSWCLOUD-22317 Required fields block issue splitting with erroneous workflow error
- Closed
-
JSWCLOUD-25300 User is not warned when completing a sprint failed or partially succeeded
- Closed
-
JSWCLOUD-26055 Splitting issues with validators on their workflow throws error
- Closed
-
JRACLOUD-81319 Issue transition button shows the wrong status when transition fails
- Gathering Impact
-
JRACLOUD-81645 Issue view > Attach button remains interactable with jira.issue.editable=false
- Gathering Impact
-
JRACLOUD-82212 The Property "jira.issue.editable" still leaves the field "Epic Link" Editable
- Gathering Impact
-
JRACLOUD-82370 500 - Internal server error displayed when adding 'Update Issue Custom Field' post function without parameters in workflow transition.
- Gathering Impact
-
JRACLOUD-83731 Copying Team field value to a single line field throws an error
- Gathering Impact
-
JRACLOUD-82448 Trying to copy a workflow with a Store Issue post function fails and produces an error
- Short Term Backlog
-
JRACLOUD-43561 Validate workflow integrity before allowing addition to workflow scheme
- Closed
-
JRACLOUD-44732 Improve error when workflow has missing add-on
- Closed
-
JRACLOUD-59736 Improve UI error messages related to workflow validators.
- Closed
-
JRACLOUD-60237 Better Warning Message For Workflow Post Functions That Will Fail
- Closed
-
JRACLOUD-62355 Better Handling of Error Message in JIRA
- Closed
-
JRACLOUD-74982 Validator displays each validation message separately
- Closed
-
JRACLOUD-75902 Improve error message returned when attempting to update an issue in a non editable workflow state
- Closed
-
JRACLOUD-80144 Customize the message displayed for workflows where the issue transition is not allowed
- Closed
-
JRACLOUD-80164 Transition screen does not render %field% correctly from the validator
- Closed
-
JRACLOUD-81572 Adding Issue type to Workflow Scheme
- Closed
-
JSWCLOUD-23173 Misleading error message when clone issue fails due to required field
- Closed
-
JRACLOUD-63563 Improve error message on 'Some issue types are unavailable due to incompatible field configuration and/or workflow associations'
- Gathering Interest
-
JRACLOUD-70549 Workflow usage warning when deleting custom fields
- Gathering Interest
-
JRACLOUD-75732 Meaningful error message instead of generic 500 Internal server error for workflows
- Gathering Interest
-
JRACLOUD-81185 Display Warning/Error Message when Add Workflow Button is Greyed Out
- Gathering Interest
-
JRACLOUD-82159 Workflow Diagram error should be more clear
- Gathering Interest
-
JRACLOUD-82321 Improve error message shown while editing a comment to the issue when jira.issue.editable is set to false
- Gathering Interest