-
Type:
Suggestion
-
Resolution: Unresolved
-
None
-
Component/s: Custom fields
-
None
-
0
When creating or modifying an issue, to assign an Insight object to a custom field you are required to use the key for the object:
This results in a pay load such as:
{
'project': {'key': 'TEST'},
'summary': 'Testing issue creation',
'description': 'Testing issue creation',
'issuetype': {'name': 'Task'},
"customfield_10200": [{"key": "Dev-13"}],
}
Usually (for me) however, the key is something that is not known without querying the Insight API.
I suggest that the value that it can use be enhanced so that either IQL or other fields can be referenced and result in a match such as:
{
'project': {'key': 'TEST'},
'summary': 'test with name',
'description': 'Another one',
'issuetype': {'name': 'Task'},
"customfield_10200": [{"iql": "name = 'Some Name' and objectType = 'Devices'"}],
}
or
{
'project': {'key': 'TEST'},
'summary': 'test with name',
'description': 'Another one',
'issuetype': {'name': 'Task'},
"customfield_10200": [{"name": "Some Name"}],
}
At present, using the PIP Jira package (appreciate this isn't managed by Atlassian) requires manual querying of the Insight API prior to creating an issue using the payloads above.