This article is for Data Center.
Problem
I have this formula in my Structure that allows me to create a ticket in another project:
if JQL {status = CLOSED AND issuefunction not in linkedIssuesOf('project in (ABC, ABCDE)', 'is child of') } :
CONCAT('{panel:borderStyle=solid|borderColor=black|bgColor=#44CD44}';
'[CAPITAMS|'URL';
'&summary=';item.key;' - '; item.Summary;
'&components=';
'&issuelinks-linktype=is%20child%20of';
'&description=';
'%7C%7CDonn%C3%A9e%7C%7CDetail';
']{panel}'
)
ELSE :
if JQL {status != CLOSED AND issuefunction not in linkedIssuesOf('project in (ABC, ABCDE)', 'is child of') } :
CONCAT('{panel:borderStyle=solid|borderColor=black|bgColor=#4CC2EB}';
'[ABC|URL';
'&summary=';item.key;' - '; item.Summary;
'&domain=';item.key;
'&root cause=';item.Root cause;
'&components=';
'&issuelinks-linktype=is%20child%20of';
'&description=TICKET%20NON%20CLOTURE%0A';
']{panel}'
)
My question is that both projects use the same custom field contexts. I need to copy this custom field to the created ticket
Note that I have some with a select list of single choice and others with a select list of multiple choice.
Solution
Structure does not actually create issues in other projects. In your case, the formula only generates a clickable link through the Structure formula that opens Jira’s “Create Issue” screen with some fields pre-filled via URL parameters. Everything that happens after clicking the link is handled entirely by Jira (or other apps like ScriptRunner), not by Structure.
Our support scope includes helping you build and format the formula inside Structure, following the content of our documentation https://help.tempo.io/structure-dc/latest/formulas .
Our support scope doesn’t include how Jira interprets URL parameters, pre-fills custom fields, validates values, or handles link issues; behavior of JQL functions like issuefunction or linkedIssuesOf (these are from ScriptRunner); support for URL parameters is also not part of the Structure Support scope. Jira fully controls this.
For questions about pre-filling custom fields (single/multi select, IDs, option names, etc.), you must check with Atlassian support for the URL parameter support in Jira and your Jira Admin for field IDs, contexts, and permissions.