Get the jira issue id from the value of a custom field

Question

I have a custom field that assosiciates a jira issue with another. I am creating a Script Field and for that I need the id of that jira issue that is assosiacted, but "issue.getCustomFieldValue(customField)" returns an Object object, I can´t get the id for that.

Is ther a way to parse it into a JiraIssue type? Can I get the id of that issue via another way?

Thanks.

Nic Brough -Adaptavist- · Answer

Ok, on both a technical and procedural level, the field does not make a child reference.  That is done with Sub-tasks, Issues, Epics, and any other issue levels you put in a hierarchy above Epic.  This field is never going to act in the way a "parent" field will.

But hey, if that's what they think they want to do, it's not for us to refuse, we can only question why they're botching something this way, explain there are better ways to do it, and then do what they think they need if they don't adopt the better approaches.

The field contains some reference to another issue.  The value in the field is not an issue, so you can't use it in your "createIssueLink" call.

You'll need to ask them how the field options relate to the issues they represent.  Issue key?  Issue id?  Another field on an issue?

Pedro Oliva Rodríguez · Answer

That is what I asked them, the answer was that this custom field makes a child reference to an issue in another issue. They want the child to be linked to the parent issue automatically

My approach was using ComponentAccessor.getIssueLinkManager().createIssueLink(sourceIssueId, destinationIssueId, issueLinkTypeId, sequence, user)

Only things I´m lacking is "destinationIssueId" which I´m trying to get retrieving the value of the custom field. Still wondering what sequence even is...

Nic Brough -Adaptavist- · Answer

No, select lists are made of options.

You can get the name of an option with issue.getCustomFieldValue(customField).getName()

Seems odd to me to want to link an issue to another one by using a select list, when the issue link function already does it.