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; } } }

Structure - can´t add an automation to a folder

Radim Drinka BS

Hi all,

I have the following use case:

We have a field called Ticket priority with the values A, B and C. When a ticket is created, the standard value is C.

We have a structure with 3 folders - A, B and C.

I want to add all the tickets to the folder C automatically (kind of a backlog). The users can then move the ticket to the folder A or B - based on their priorisation.

So they move the ticket manually and then they change the value in the field to A or B afterwards.

Long story short - A and B folders are managed manually, C is filled automatically. The order /kind of rank) of the issues in the folders should also be done manually.

It is not possible to insert issues to folder C, I receive the famous message "You are about to create a generator. It will be impossible to add it to the structure because of the automation installed: Cannot add generators to dynamic content. You can drag-and-drop the item to a different location.".

The original request was: "when I move the issue to the folder A, the value in the field Ticket priority changes automatically to A" - but this is another story :-) First I need to get all the tickets to the C folders.

Any advices or hints?

Thank you all!

Regards

Radim

Comments

David Niro

Hello @Radim Drinka BS ,

David from ALM Works here.

Rather than creating folders for A, B and C, you can instead Group by your Team field using a Group Generator. When creating the generator, make sure that the "allow changes via Structure" option is enabled. You will also want your Insert Generator to be outside of the folder

This will allow you to move the issues between groups and have the field value change.

Please let me know if this helps!

Best Regards,
David

Radim Drinka BS

Hi David,

thanks for your swift response.

This was my first idea but I think if I group the the issues by the field Ticket priority I will not be able to add additional rules later. Folders allow that because of separate automation rules on the folder level.

Anyway - I will discuss this with the requester whether any additional behaviour within A,B and C priority is to be expected. If not, I will suggest grouping.

Thanks again

Regards

Radim

Radim Drinka BS

Hi David,

the customer finds this idea good, but we are facing some funny thing:

The setup:

Any hint what we are doing wrong?

Thanks

Regards

Radim

David Niro

Hello @Radim Drinka BS ,

Glad to hear the customer likes the idea!

From your screenshot, I can see the hand icon next to RAMS-388. This indicates that the issue was moved here through Manual Adjustments.

Manually adjusted issues ignore generators and can be placed anywhere in the structure arbitrarily, which is why you see it under the wrong group.

You can Undo Manual Adjustments by moving the issue back to its original position, or by disabling them for the entire structure.

I would recommend disabling them for the structure. Since you are now grouping by a field, you can move issues between groups to change the value for the field. If the customer is also looking to move issues up and down the hierarchy within the group, I would recommend using a Sort by Rank generator.

Please let me know if this helps!

Best Regards,
David

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server

structure

jira-data-center

data-center