workflow to stop stage change to close if specific fields are not populated on ticket
ART-15716_KNOWLEDGE_NODE-31
conditions While creating custom schema\n\nThis can be handled by our team. Kindly reach out to us, and we\xe2\x80\x99ll be happy to assist you with setting up a custom schema. Would you like us to create a ticket for this?\n\nAPI for stage customizationThis can be handled by our team. Kindly reach out to us, and we\xe2\x80\x99ll be happy to assist you with setting this up. Would you like us to create a ticket for this?\n\nStage customization (e.g., customizing workflow stages for tickets,
Support queries related playbook
ART-15487_KNOWLEDGE_NODE-48
... // no changes |\n| > | ] |\n| > | }\' |\n```\n\nAll objects of the *bug* subtype now adhere to the stage diagram created above.\n\nConfigure dependent fields\n--------------------------\n\n##### \n\nThe developers in your organization tend to forget to add an RCA when resolving the\nbugs. You can make the *RCA* field required when a *bug* object is moved to the\n*completed* stage by adding a dependent field constraint.\n\n```\n|  |  |\n| --- | --- |\n| $ | curl --location
Object customization | DevRev | Docs
ART-1645_KNOWLEDGE_NODE-53
\n    >|     "leaf_type": "issue",  \n    >|     "subtype": "bug",  \n    >|     "fields": [  \n    >|         ... // no changes  \n    >|     ],  \n    >|     "conditions": [  \n    >|         {  \n    >|             "expression": "stage == \'don:core:dvrv-us-1:devo/test:stage/5\'",  \n    >|             "effects": [  \n    >|                 {  \n    >|                     "fields": [ "custom_fields.rca" ],  \n    >|                     "require": true  \n    >|                 }  \n    >|
Object customization (Beta) — DevRev | Docs
ART-15487_KNOWLEDGE_NODE-50
"fields": [ "custom_fields.rca" ], |\n| > | "require": true |\n| > | } |\n| > | ] |\n| > | } |\n| > | ] |\n| > | }\' |\n```\n\nAny attempt to update a *bug* object to the *completed* stage without populating\nthe *RCA* field is rejected.\n\nThe supported operators are `==`, `!=`, `&&`, `||`. The `expression` is a\nbinary expression that must return a boolean value.\n\nThe `effects` array contains the list of effects of the condition. The following effects are supported:\n\n* `require`: Whether
Object customization | DevRev | Docs
ART-1645_KNOWLEDGE_NODE-54
]  \n    >|         }  \n    >|     ]  \n    >| }\'\n[/code]  \n  \nAny attempt to update a _bug_ object to the _completed_ stage without populating the _RCA_ field is rejected.\n\nThe supported operators are `==`, `!=`, `>`, `>=`, `<`, `<=`. The `expression` is a boolean expression that must return a boolean value.\n\nThe `effects` array contains the list of effects of the condition. The following effects are supported:\n\n  * `require`: Whether the field must be set for the condition
Object customization (Beta) — DevRev | Docs
ART-1645_KNOWLEDGE_NODE-52
developers in your organization tend to forget to add an RCA when resolving the bugs. You can make the _RCA_ field required when a _bug_ object is moved to the _completed_ stage by adding a dependent field constraint.\n\n[code]\n\n    $| curl --location \'https://api.devrev.ai/schemas.custom.set\' \\  \n    ---|---  \n    >| --header \'Content-Type: application/json\' \\  \n    >| --header \'Authorization: Bearer <TOKEN>\' \\  \n    >| --data \'{  \n    >|     "type": "custom_type_fragment",
Object customization (Beta) — DevRev | Docs
ART-15487_KNOWLEDGE_NODE-51
the field must be set for the condition to be met.\n* `show`: Whether the field must be shown for the condition to be met.\n* `allowed_values`: The conditional allowed values for the enum type field.\n\n##### \n\n`don:core:dvrv-us-1:devo/test:stage/5` is the ID of the *completed* stage. The\nstage display name is not used in the expression because it is liable to change.\n\nConstraints on stock fields can only be strengthened.\nFor example, a required stock field cannot be made optional, and a
Object customization | DevRev | Docs
ART-1645_KNOWLEDGE_NODE-55
to be met.\n  * `show`: Whether the field must be shown for the condition to be met.\n  * `allowed_values`: The conditional allowed values for the enum type field.\n\n#####\n\n`don:core:dvrv-us-1:devo/test:stage/5` is the ID of the _completed_ stage. The stage display name is not used in the expression because it is liable to change.\n\nConstraints on stock fields can only be strengthened. For example, a required stock field cannot be made optional, and a hidden stock field cannot be made
Object customization (Beta) — DevRev | Docs