Hi,
I'm trying to set a custom field to empty using the Jira Automation rule "Edit field, advanced". The custom field is Parent Link, also customfield_12100. I can retrieve its info as I previously check a condition like this {{issue.customfield_12100.data.issueType.id}} and it works.
I get the JSON format using the jira API rest and this is it (it's within fields):
"customfield_12100": {
"hasEpicLinkFieldDependency": true,
"showField": true,
"data": {
"id": 96904,
"key": "JOE-32",
"keyNum": 32,
"summary": "JOE Saga test1",
"projectId": 12322,
"issueType": {
"id": "10649",
"iconUrl": "/secure/viewavatar?size=medium&avatarId=17582&avatarType=issuetype"
}
}
},
The goal is to set it to Empty so that custom field does not have a value. I've tried with the update + set method and also fields as described in the following link with no success: https://support.atlassian.com/jira-software-cloud/docs/advanced-field-editing-json/
I'm doing it with an Advanced Field edit because there's a bug and Parent Link is not a selectable field in the Edit issue action dropdown (see image).
Any chance on knowing why I can't do so or how to do it properly?
Thank you.
I finally got this to work, let me provide the JSON:
{
"fields": {
"customfield_12100": null
}
}
Thanks everyone for being involved!
I was knocking my head against a wall too regarding what parameters to use for amending a number of a custom field in Advanced Json for automation rules. It's in the documentation that merely states what you changed to above!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Are you using a company-managed (classic) or team-managed (next-gen) project? I am going to assume Team-Managed for now...
If you want to clear the parent (epic) of an issue (story, task, bug), you can use this JSON:
{
"fields": {
"parent": { "id": null }
}
}
Best regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Bill Sheboy
I'm using a company-managed project and it didn't work for me. Nevertheless, I'm not interested in changing the Epic, I want to change a different parent, it's a custom issue type at the same level as Epics, so in child issues I have to reference it as Parent Link, not Epic Link, nor "issue is Parent of" by linking issues.
Thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I suggest using the method described in this article to learn if your field has a smart value which can be accessed by automation rules:
https://support.atlassian.com/jira-software-cloud/docs/find-the-smart-value-for-a-field/
If so, it may reveal a different name and structure in the JSON than what you expected when trying the edit.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the link to the doc! Unfortunately, I already tried that out and couldn't do anything useful with it. As I said, I can retrieve info from this custom field but nothing more than that.
I also checked the edit meta with no success: https://<yourinstanceurl>/rest/api/3/issue/<issuekey>/editmeta
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Sergio Montávez at this point I am unclear what else to try. As you are the site admin of a paid license for Jira, you should be able to create a support ticket to Atlassian to see if they have ideas: https://support.atlassian.com/contact/#/
If you learn anything from them that helps please consider posting the information back here so the rest of the community can benefit. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi again @Bill Sheboy
I submitted a ticket to their support team at the same time that I posted this topic. Conversations are already going but there's no conclusion yet. Once I have anything final I'll post it here.
Thank you for being involved!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.