trying to add component using smart value user input

[Sean Hagans]

I've got 2 projects (we'll say ABC and XYZ for ease) and am creating a rule to clone an issue from one to the other. 

They have different components. 

I have a rule in ABC that is triggered manually and prompts for user input. The desire is for a user input dropdown selection of XYZ project components. 

I have already looked for ways to populate that dynamically with XYZ components and gave up on that. Instead I have an option in that dropdown for each component in XYZ that I explicitly created on the rule. 

So in this case, my XYZ project has the following components (comp1,comp2,comp3). my rule in ABC has user input prompt "add component" that has the options comp1,comp2,comp3 and the name is RemoteComponent

My rule in ABC does a clone issue into XYZ and I have setting for Component field with a value of {{userInputs.RemoteComponent}}. 

After that my rule makes a comment on the ABC issue. 

When I run this action, I get an error on clone while parsing additional fields for invalid JSON. 

Is it possible to set a component with a smart value? 

[Kalyan Sattaluri · Accepted solution]

Hello @Sean Hagans 

Welcome and Please share screenshot of your clone issue, especially this component field and how are your formatting your JSON. It has to be in certain format as listed here.  Thanks!

[Sean Hagans]

I'm not editing JSON directly. I'm just using the UI option to set a field in the clone issue action. 

What I have at this point is super basic and literally just trying to add a user input smartvalue into the components field. 

[Bill Sheboy]

Hi @Sean Hagans -- Welcome to the Atlassian Community!

Would you please post an image of the audit log details from the rule execution, showing the error?  Thanks!

Kind regards,
Bill

[Kalyan Sattaluri]

Hello, So user can choose 1 value from the dropdown when triggering this rule? And these values "Comp1", "Comp2"etc..are components names?

[Sean Hagans]

the error is silly simple

______

Yes the Comp1 and Comp2 are component names in the target remote project.

[Sean Hagans]

I have not edited the JSON, but here are the contents of the additional fields on the Clone Issue action.

{
    "update": {
      "labels": [
        {
           "add": "cloned"
        }
      ],
     "components": [
       {
          "add": {
            {
              {{userInputs.RemoteComponent}}
            }
        }
     }]
  }
}

[Bill Sheboy]

I was hoping to see the entire log entry, not just the error, for some context.  Regardless...

I wonder if the rule got "glitched", with something stored in the advanced edit section which is not displaying.  Two ways to check that are:

1. Disable the rule, wait a few seconds, re-enable it, and re-test.  If that does not help...
2. Disable the rule, and re-create it from scratch.  Then re-test.

Rules can get "glitched" from too many edit / publish cycles, and so those actions can help to detect that problem.

Update, based on your last post: the problem is there is JSON trying to edit the field and it is selected from the dropdown list.  Only one of those techniques may be used for a field in a single issue edit action.

[Sean Hagans]

For anyone replying, have you tried what I'm doing? Has anyone successfully used a userInput or general smart value as a value on components field? 

I'm assuming by the way people are asking that this is something that you've seen work and know it should work, and thus the only way it wouldn't be working is if I'm doing something wrong, is that correct?

[Sean Hagans]

well I'm not doing any of that, I just added the components edit to the clone. Jira did the rest. Do I need to remove the JSON or something? I didn't write it or make it, I just looked at it by expanding that UI item at the bottom of the panel.

Also this is the 4th time I've made this same rule from scratch. It's literally as simple as I've put it here. 

1. Select new rule

2. Set as Manual trigger - check box to ask for input field - set field name, add values, set smartvalue name

3. Add Clone issue - set target project - add the set component - add smartvalue of input field as value for set component

Done. That's it. No other actions on this, no editing of defaults, literally just those 3 things. Repeated 4 times with the same failures.

[Kalyan Sattaluri]

Hello @Sean Hagans 

Please dont get mad on Friday. We are just trying to help. LOL.

Remove the components selection from drop down.

In the JSON section, replace existing contents with below and retrigger the rule.

{
"update": {
"labels": [
{
"add": "cloned"
}
],
"components": [
{
"add": {
"name": "{{userInputs.RemoteComponent}}"
}
}
]
}
}

[Sean Hagans]

I'm not angry, I just want to make sure I don't confuse people into thinking that I'm doing something other than selecting the UI options. I am also legitimately asking if anyone replying has done this or is doing this with success. No one has said "it works for me, here's what I have that is working". So I want to make sure that answers are related to finding out what is non-standard about mine rather than asking me to try things without knowing if it should work out of the box.

Removing the component edit from the clone and replacing the auto-generated "additional fields" JSON with yours results in a 400. 

Not sure if that's progress or not.

[Kalyan Sattaluri]

Hello @Sean Hagans 

I have sucessfully tested your rule.

As you can see from my screenshot, my advanced JSON did not auto-populate with "components" object by itself.

One final try, delete everything in Advanced Section, redo the components drop down with your initial smart value, BUT, specifically choose the Issue Type..

[Sean Hagans]

hey that worked! Thanks! 

I'm not sure why it's auto-populating on my side, but when I remove that manually and hit update, I get what you have there. I just recreated a new rule and it did the same thing. 

Looks like the problem is that for whatever reason, my rule is auto-generating a JSON in additional fields when I add a component field edit and that is messing it up. Removing that makes it work.

Thanks for the help.

[David Ortiz Bollain]

Hello!
Thank you for your support.

This seems not to be compatible with Compass components.

I'm fetching the component name from the commit, when adding it to the Components field, it's added as a non Compass Component even if the name already is present in Compass Components.

Has anyone be able to avoid Compass Components to be manually added?

Thank you