hi_jira2/models/
multiple_custom_field_values_update.rs

1/*
2 * The Jira Cloud platform REST API
3 *
4 * Jira Cloud platform REST API documentation
5 *
6 * The version of the OpenAPI document: 1001.0.0-SNAPSHOT
7 * Contact: ecosystem@atlassian.com
8 * Generated by: https://openapi-generator.tech
9 */
10
11/// MultipleCustomFieldValuesUpdate : A custom field and its new value with a list of issue to update.
12
13
14
15#[derive(Clone, Debug, PartialEq, Default, Serialize, Deserialize)]
16pub struct MultipleCustomFieldValuesUpdate {
17    /// The ID or key of the custom field. For example, `customfield_10010`.
18    #[serde(rename = "customField")]
19    pub custom_field: String,
20    /// The list of issue IDs.
21    #[serde(rename = "issueIds")]
22    pub issue_ids: Vec<i64>,
23    /// The value for the custom field. The value must be compatible with the [custom field type](https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-custom-field/#data-types) as follows:   *  `string` the value must be a string.  *  `number` the value must be a number.  *  `datetime` the value must be a string that represents a date in the ISO format or the simplified extended ISO format. For example, `\"2023-01-18T12:00:00-03:00\"` or `\"2023-01-18T12:00:00.000Z\"`. However, the milliseconds part is ignored.  *  `user` the value must be an object that contains the `accountId` field.  *  `group` the value must be an object that contains the group `name` field.  A list of appropriate values must be provided if the field is of the `list` [collection type](https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-custom-field/#collection-types).
24    #[serde(rename = "value")]
25    pub value: Option<serde_json::Value>,
26}
27
28impl MultipleCustomFieldValuesUpdate {
29    /// A custom field and its new value with a list of issue to update.
30    pub fn new(custom_field: String, issue_ids: Vec<i64>, value: Option<serde_json::Value>) -> MultipleCustomFieldValuesUpdate {
31        MultipleCustomFieldValuesUpdate {
32            custom_field,
33            issue_ids,
34            value,
35        }
36    }
37}
38
39