Nested displayOptions for having multiple fields with the same name

cmprmsd · April 23, 2021, 3:35pm

I am trying to extend the Taiga node with support for tasks and userstories.
There is one field, called status, that is implemented in all three types but is just called status.

I have two ways of implementing them. One working, but ugly, one more smooth, but not working.
Maybe you can give me an advice, why it does not work.

First working solution is to create all additional fields three times with display options for each of them like the following:

		displayOptions: {
		show: {
			resource: [
				'issue',
			],
			operation: [
				'create',
			],
		},
	},
do stuff.. another display options, same do stuff but with the one status field formatted different.

This solution works but I’m not satisfied with it to make a PR.
See the changes:
https://github.com/cmprmsd/n8n/commit/ad2a97e9e02b2a7cc510cc51e9c105f132f789a7

So I thought of nesting display options but that does not work for me:

displayName: 'Update Fields',
	name: 'updateFields',
	type: 'collection',
	placeholder: 'Add Field',
	default: {},
	displayOptions: {
		show: {
			resource: [
				'issue',
				'userstory',
				'task',
			],
			operation: [
				'update',
			],
		},
	},

and then I would have only to customize fields that are named the same in different contexts:

{
			displayName: 'Issue Status ID',
			name: 'status',
			type: 'options',
			displayOptions: {
				show: {
					resource: [
						'issue',
					],
					operation: [
						'update',
					],
				},
			},
			typeOptions: {
				loadOptionsMethod: 'getIssueStatuses',
			},
			default: '',
		},
		{
			displayName: 'User Story Status ID',
			name: 'status',
			type: 'options',
			displayOptions: {
				show: {
					resource: [
						'userstory',
					],
					operation: [
						'update',
					],
				},
			},
			typeOptions: {
				loadOptionsMethod: 'getUserstoryStatuses',
			},
			default: '',
		},
		{
			displayName: 'Task Status ID',
			name: 'status',
			type: 'options',
			displayOptions: {
				show: {
					resource: [
						'task',
					],
					operation: [
						'update',
					],
				},
			},

Do I have to go with option one and have tons of duplicated text?

RicardoE105 · April 23, 2021, 4:28pm

You can just one collection and control what is shown inside using the displayOptions. However, with an small tweek. Let’s say that we have a collection called additonalFields that will be shown when the resource is issue and the operation is created and updated. It should look like:

displayName: 'Additional Fields',
	name: 'additionalFields',
	type: 'collection',
	placeholder: 'Add Field',
	default: {},
	displayOptions: {
		show: {
			resource: [
				'issue',
			],
			operation: [
				'update',
                            'create''
			],
		},
	},

Within the collection, we have two fields: status and name. We want to show the field status when the operation is update and the field name when the operation is create. To achieve that, the fields should be configured/setup as follow:

displayName: 'Status',
	name: 'status',
	type: 'string',
	default: {},
	displayOptions: {
		show: {
			resource: [
				'/issue',
			],
			operation: [
				'/update',
			],
		},
	},


displayName: 'Name',
	name: 'name',
	type: 'string',
	default: {},
	displayOptions: {
		show: {
			resource: [
				'/issue',
			],
			operation: [
				'/create',
			],
		},
	},

Noticed the difference? To use a displayOptions within a collection the value need the prefix /.

Let me know that helps.

cmprmsd · April 24, 2021, 11:38am

Thanks for your reply. I can’t get it to work though.

See the example here:

{// Global Update Fields
	displayName: 'Update Fields',
	name: 'updateFields',
	type: 'collection',
	placeholder: 'Add Field',
	default: {},
	displayOptions: {
		show: {
			resource: [
				'issue',
				'userstory',
				'task',
			],
			operation: [
				'update',
			],
		},
	},
	options: [
              {
			displayName: 'Assigned To',
			name: 'assigned_to',
			type: 'options',
			typeOptions: {
				loadOptionsDependsOn: [
					'projectId',
				],
				loadOptionsMethod: 'getProjectUsers',
			},
			default: '',
			description: 'User id to you want assign the issue to',
		},
{
			displayName: 'Issue Status ID',
			name: 'status',
			type: 'options',
			typeOptions: {
				loadOptionsMethod: 'getIssueStatuses',
			},
			displayOptions: {
				show: {
					resource: [
						'/issue',
					],
					operation: [
						'/update',
					],
				},
			},
			default: '',
		},
		{
			displayName: 'User Story Status ID',
			name: 'status',
			type: 'options',
			typeOptions: {
				loadOptionsMethod: 'getUserstoryStatuses',
			},
			default: '',
		},
		{
			displayName: 'Task Status ID',
			name: 'status',
			type: 'options',
			displayOptions: {
				show: {
					resource: [
						'/task',
					],
					operation: [
						'/update',
					],
				},
			},
			typeOptions: {
				loadOptionsMethod: 'getTaskStatuses',
			},
			default: '',
		},

In this example only the User Story Status ID gets displayed and of course for all three (task,story and issue).

With the display options within display options, it just gets never displayed.

RicardoE105 · April 24, 2021, 12:18pm

Can you please create a PR as a draft so that I can test it?

cmprmsd · April 24, 2021, 1:19pm

Sure!
https://github.com/cmprmsd/n8n/commit/e6f5609c00cf67dfa88c0241660574355574247d

For easy reference to my second way there is the copy of issueOperationFields.ts. I haven’t managed to cleanup the naming yet

cmprmsd · May 3, 2021, 1:43pm

Did you have a change to test it out?
If not, I’ll just write it the way it’s working for me and create a PR, where changes might be needed then

RicardoE105 · May 3, 2021, 8:49pm

Sorry, have been quite busy. Send the PR and will check it out there.

theneilkirk · July 9, 2021, 2:50pm

Hi

I’m wondering if this has progressed any?

I’m interested in the Tasks and Stories features too wish I could contribute but I’m not really a developer…

cmprmsd · July 9, 2021, 10:34pm

Hey,
I started a merge request.

github.com/n8n-io/n8n

Add Taiga functionality for User Stories and Tasks

n8n-io:master ← cmprmsd:master

opened 10:45PM - 14 Jun 21 UTC

cmprmsd

+931 -387

As some people discussed here (https://community.n8n.io/t/taiga-project-manageme…nt-partly-created/2138) Taiga provides more features for API interaction. I added some functionality to create, update and get `tasks` as well as `user stories` in addition to the existing `issues` integration. As discussed in https://community.n8n.io/t/nested-displayoptions-for-having-multiple-fields-with-the-same-name/5431 I tried nesting the displayOptions, which did not work for me. So I circumvented this problem by copying the operationFields. I'm not able to come up with the correct implementation and hope you can help me out merging these changes into your project. The code is working so far. I tested several automations with triggers e.g. changing user story status id's when a task within a story is closed. Maybe some do-betters for future updates on this node: * split the operationFields into multiple files for better readability * Instead of copying all fields for each type aggregate all overlapping fields that the different types have in common (e.g. `assigned_to` etc.) I hope this can be merged though and worked on in future updates as it provides already some additional functionality! Feel free to edit :+1:

However ivov created another merge request and I’m happy if his will be merged

github.com/n8n-io/n8n

Expand Taiga node

n8n-io:master ← n8n-io:taiga-node-expansion

opened 09:52AM - 06 Jul 21 UTC

ivov

+2877 -699

This PR expands the Taiga node: ``` epic ├── create ├── delete ├── …update ├── get └── getAll issue ├── create ├── delete ├── update ├── get └── getAll task ├── create ├── delete ├── update ├── get └── getAll userStory ├── create ├── delete ├── update ├── get └── getAll ``` Relates to #1896.

Just follow both topics and you’ll be posted

theneilkirk · July 10, 2021, 12:30pm

Awesome. Subscribed!

Jihad · November 19, 2024, 12:42pm

Hey, 3 years later lol.

Is the feature of having specific display rules in the Options of collection, got removed or changed? As i have lots of collections with many options but only one or two options differs based on operation… and seems redundant to duplicate that collection multiple times with small differences .

As now if i did it, i get:

Problem running workflow

Could not resolve parameter dependencies. Max iterations reached! Hint: If displayOptions are specified in any child parameter of a parent collection or fixedCollection, remove the displayOptions from the child parameter.

This is a snippets of one of the implementation needs for it:

{
    displayName: 'Transaction Call Settings',
    name: 'transactionSettings',
    type: 'collection',
    placeholder: 'Add Transaction Settings',
    default: {},
    displayOptions: {
        show: {
            resource: ['transactions'],
            operation: ['createTransaction', 'updateTransaction'],
        },
    },
    options: [
        {
            displayName: 'Error If Duplicate Hash',
            name: 'error_if_duplicate_hash',
            type: 'boolean',
            default: true,
            description: 'Whether to throw an error if a duplicate hash is detected',
	        displayOptions: {
				show: {
					resource: ['/transactions'],
					operation: ['/createTransaction'],
				}
                },
	},
        {
            displayName: 'Apply Rules',
            name: 'apply_rules',
            type: 'boolean',
            default: false,
            description: 'Whether to apply rules to the transaction',
        },
        {
            displayName: 'Fire Webhooks',
            name: 'fire_webhooks',
            type: 'boolean',
            default: true,
            description: 'Whether to trigger webhooks for the transaction',
        },
        {
            displayName: 'Group Title',
            name: 'group_title',
            type: 'string',
            default: '',
            description: 'Title for grouping split transactions',
        },
    ],
},