create URL with smart values

[Rob Peterson]

I'm trying to create a URL that will populate a custom field.  The URL remains static except for a variable that is contained within another custom field in the issue.  

• Custom field 1: 123456
• Custom URL field (intended result): https://www.url.com/q?z=123456

I'm able to create url properly so that it shows in the log for the rule, however, in usage, the rule will fail with "Operation value must be a string".  Example of what I've used:

[Rob Peterson · Accepted solution]

I've altered the field type from URL to the standard text field.  The UI recognizes the text as a URL and automatically makes it actionable (i.e. user can click on to open new tab/browser for the URL).

[John Funk · Accepted solution]

Hi Rob,

What type of field is URL?

What's the relationship of the custom field value to the issue that it is connecting to? 

Can you share more about the rule? Type of trigger? Conditions? etc. 

[Rob Peterson]

Sure, the field type is "URL".

Not sure I fully understand the relationship question... but the URL Custom Field (Custom Field 2 - destination) is a custom field in the issue where as Custom Field 1 (source) is in the parent.

Currently, the rule itself is on issue create.  The only condition is that is not an Epic or Story.  The Epic or Story would contain the information as the parent.  I'm currently able to successfully copy the field down to the child from the parent issue when it's going from the custom field 1 to custom field 1 place holders (ie. ChildIssue.CustomField1 is sourced by ParentIssue.CustomField1 on creation).  The rub is when I'm trying to create the URL.  I'm not sure if there is some special way since it's a "URL" type field instead of a "string" but the error states it's expecting a string...

[Rob Peterson]

This may help:

[John Funk]

Maybe if you experiment with a regular short text field type instead of a URL field type it might work. 

[bmccoy]

Hi Rob,

I've had a bit of a play around with the URL custom field and copying values from the parent, and everything seems to be behaving as expected.

It might be worth reaching out to our support team as it is possibly something specific to your setup.   We can then have a closer look at your rule and the logs to see what might be happening.

Cheers,
Brydie
[Automation for Jira]

[Rob Peterson]

Can you share the rule here?