I checked the Jira Administration section on a sample account and there isn't a stock Requirements field which makes me think it is a custom field in your cloud installation (unless your are using a server installation).
Can you clarify if you are using cloud or server impleentation? I can't tell from the url you specified if it is a hosted jira server implementation or a custom url for a cloud implementation.
If it is a cloud implementation, can you make a python rest api GET call to the following JIRA REST V3 API named field
https://sample_company.atlassian.net/rest/api/3/field
Make sure to update the url with your cloud instance or it will fail as sample_company isn't a real domain.
That will return all the fields whether they are system or custom in json format. You can then parse the json to find the field(s) once you know the field names. Here is the structure of a sample field from a sample jira cloud installation for reference
{
"id": "customfield_10072",
"key": "customfield_10072",
"name": "samplefield",
"custom": false,
"orderable": true,
"navigable": true,
"searchable": true,
"clauseNames": [
"cf[10072]"
],
"schema": {
"type": "string",
"system": "samplefield"
},
"customId":10072
},
The name
will most likely be Requirements
for the custom field you are lookiing for since that is what is rendering in the screenshot but id and key for the field will have a name such as customfield_NNNNN where the NNNNN is a custom number depending on how many custom fields you have in your installation. Once you know this id
or key
, you can make a python rest api call to the JIRA REST V3 API for your issue and get the custom field values from the previous API. This will change from customer install to customer install so I can't give the exact field.
Here is the Jira Rest API for an issue for example:
https://sample_company.atlassian.net/rest/api/3/issue/jira_ticket
where jira_ticket is the name of the jira_ticket you are trying to get the data from.
So for example if my ticket is XX-13515, I would make a GET Request to
https://sample_company.atlassian.net/rest/api/3/issue/XX-13515
That would return JSON output. You could then parse the results for the customfield_NNNN for your Requirements
field and the other field you are looking for. There could be multiple ways you would find the field in the results for your issue such as:
{
"id": "customfield_10027",
"key": "customfield_10027",
"name": "Requirements",
"untranslatedName": "Requirements",
"custom": true,
"orderable": true,
"navigable": true,
"searchable": true,
"clauseNames": [
"cf[10027]",
"Requirements",
"Requirements[Paragraph]"
],
"schema": {
"type": "string",
"custom": "com.atlassian.jira.plugin.system.customfieldtypes:textarea",
"customId": 10027
}
},
or it could be a simple url such as
"customfield_10072": null,
or possibly some other type. So anything would else be speculation at this point without some sample results from you to investigate further.