Struct FieldSpec 

pub struct FieldSpec {
    pub key: String,
    pub name: String,
    pub field_type: String,
    pub items: Option<String>,
    pub required: bool,
    pub readonly: bool,
    pub category: Option<String>,
    pub options: Option<FieldOptions>,
}

One field’s definition: what it holds, whether it can be written, and what values it accepts.

queue fields lists the keys; this answers the question that follows, which is the one --set is otherwise guessing at.

Fields

key: String

name: String

field_type: String

string, float, user, datetime — Tracker’s own vocabulary, which is what its error messages quote back.

items: Option<String>

What one element is, when the field holds several of them. None means the field takes a single value.

required: bool

readonly: bool

category: Option<String>

Where Tracker files the field: Системные, Agile, and whatever the organisation added. In the organisation’s own language.

options: Option<FieldOptions>

How the accepted values are decided, when they are decided at all.

Trait Implementations

impl Clone for FieldSpec

fn clone(&self) -> FieldSpec

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for FieldSpec

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Serialize for FieldSpec

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.