nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

userInputs was removed from Smart Value fields?

John_it6x5d

This was working fine and is now broken. Using Cloud version.

The problem seems to be the user input variable. More specifically:

(1) We have a Manual Trigger rule that requests user input for variable NewTitle

(2) Next step copies the current page to a new space and new page, and sets the title from the smart value {{userInputs:NewTitle}}

This stopped working and now we can't find the answer for making user inputs function on the following step. The userInputs does not seem to be available as an option now, it's just gone from the menus. If it was renamed we can't find it.

What changed? Is there a new way to do this?

Accepted answers

All comments

Rick Westbrock

I thought the syntax for the user input value uses a dot instead of a colon i.e. {{userInputs.NewTitle}}

John_it6x5d

That may be a typo... Whatever the format is, we don't see userInputs in the menu now at all.

John_it6x5d

When we use { } smart tags and search for 'user' it has 5 results
{{user.accountId}}

No {{userInputs.variable}}

and search for 'input' and zero matches.

John_it6x5d

We didn't change anything. The automation was tested and running fine for weeks. It simply does not run now when manually triggered. It only has 3 steps so it wasn't hard to find the issue.

Take out the {{userInputs.NewTitle}} and it works again.

Bill Sheboy

Hi @John

For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas. Thanks!

Until we see those...

I see you also posted a question about this topic here: https://community.atlassian.com/t5/Automation-articles/Request-input-from-users-when-a-Manual-rule-is-triggered/bc-p/2738281#M1701 Perhaps continue with this thread to focus the suggestions.

Once you post your rule, actions, and audit log details we can help track down the symptom and possible causes.

Kind regards,
Bill

John_it6x5d

Thanks... I get it. I can share but it's not troubleshooting the automation sequence or coding.

Sorry, I posted the broader question to the other thread as it related to the specific feature.

... that Title smart tag was there before and working.
If I click on the {} button we don't see any support for userInputs now:

When triggered, it asks me for the input as expected.

The next response is this. No audit log entry is made.

John_it6x5d

I'm relatively new to writing automation rules here in Jira/Confluence... so if I'm doing something dumb here, let me know. But I thought I'd avoided stupid user tricks because this ran 100 times successfully before failing and when I tried to recreate a new rule for testing I discovered the userinput is still valid on the first task but not the second.

Bill Sheboy

No worries; we are all learning new things all the time.

That lookup for smart values with {_} is a relatively new automation editor feature, and certainly does not list all possible smart values. It even has typos for some of them.

And my understanding is it is not dynamic; it is static and based on another version of the documentation. That is, it is unlikely to show the names of the fields you added to the Manual Trigger for user inputs for a specific rule.

Back to the rule's audit log, please post an image showing the details under "Show more" for when you tried to execute the rule.

I did see an open defect for intermittent problems with the Copy Page action when some third-party, marketplace Confluence addons are used. Do you have any of those installed? (Your Jira site admin will know this.)

John_it6x5d

And it seems to be working again magically after several weeks of downtime. Not sure what changed or where but it wasn't my script.

I can confirm it works now AND the userInputs.variable does NOT show up in the search documentation. So the lack of documentation was a red herring (misleading).

So really nothing to go on in order to make any conclusion, Other than it seems the feature is valid at this time.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

questions-for-confluence

automation

questions-for-confluence-cloud