Using the rest API, I’m trying to find a way to easily distinguish the “Start Date” fields in Jira Cloud and in Jira Data Center from all other fields.
On Jira Server, there is a “Target Start” field and this is the API response for that field.
{
"id": "customfield_10109",
"name": "Target start",
"custom": true,
...
"schema": {
"type": "date",
"custom": "com.atlassian.jpo:jpo-custom-field-baseline-start",
"customId": 10109
}
},
Looks like the custom
is unique, so I should be able to always find this field for any instance. Just wanted to confirm that my assumption is correct for Jira Server?
For Jira Cloud, the custom seems generic so I don’t think I can use that to distinguish from other date fields. However, I’ve noticed that the key is the same across two different instances that I have access to. Is that a coincidence? Or is the key for “Start Date” in Jira Cloud guaranteed to be “customfield_10015” across all instances?
{
"id": "customfield_10015",
"key": "customfield_10015",
"name": "Start date",
"untranslatedName": "Start date",
"custom": true,
...
"schema": {
"type": "date",
"custom": "com.atlassian.jira.plugin.system.customfieldtypes:datepicker",
"customId": 10015
}
},