Is there a way to concatenate or nest smart values?

[Michael Spoonauer]

I'm using Automation for Jira to automatically create a comment if the Approving Role for the current sub-task is "name of the role" but the value of the "name of the role" field within the parent of the sub-task does not equal the initiator of the workflow transition.

Instead of having to add if/else statements for every possible value {{issue.parent.name of the role.name}}, where "name of the role" is both the value of the sub-task's "Approving Role" field and the name of the custom field in the parent from which to grab a username for comparison to the initiator name, it would be great if the following were supported:

Condition:

{{initiator.name}}

does not equal

{{issue.parent.{{issue.Approving Role}}.name}}

[Mizan]

I guess all your three projects are using the same screen scheme or view screen .

[Nic Brough -Adaptavist-]

Forget about "screens".

You need to look at the "field configuration" - that carries the mandatory / optional flags.  The screens have nothing to say about whether a field is optional or mandatory.  You'll need a field configuration for each set of different mandatory/optional flags that you want on fields

[Narayanan Subramanian]

Guys,

As I said, yes I tried field configuration and I fully understand that the issue is not with respect to screens at all. But please note this is not a custom field that I am using and I don't see any option to configure a field which is not custom. Do we have any options to configure a non custom field? Please refer my screenshots below. I can see configure option for custom fields but for for system default fields.

image2014-12-11 9:13:29.png

image2014-12-11 9:17:3.png

Cheers

Narayanan P.S.

[Nic Brough -Adaptavist-]

ALL the fields are listed in the field configurations. The only field you cannot make optional is "summary" I've no idea what you think you're looking at, because a field configuration lists all fields.

[Narayanan Subramanian]

Nic, I am looking at the same field configuration you are mentioning and I am able to see all the fields on the configuration. I have just cut that specific field alone on the screenshot and pasted it here to show that the configure option for the system default field is not available. Please go through my question again. I am not concerned about how to make the field optional or mandatory which I know how to do. But I 'm concerned about why the field being visible post submitting an issue even though it is not included for the project and as the field is not an custom field its not configurable.

[Narayanan Subramanian]

I am sorry, probably my question is misleading "Getting Field is mandatory for field that is not included in the screen". It should be "Field displayed post the issue is created which is not part of the project"

[Nic Brough -Adaptavist-]

Yes, it's been confusing me. To hide system fields, you can use the field configuration option of "hide".

[Joe Pitt]

Requiring fields at creation is done in the field configuration scheme for the project/issue type combination. It is handled by a plugin if required during a transition. It could be the jira-suite-utilities or behavior plugin.