Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

When creating new structures, there are a number of steps you can take to improve the performance or usability of the structure. In the following document, we've gathered some of the best tips from our users and developers for getting the most out of Structure.

Table of Contents
maxLevel2
minLevel2

Use Group generators instead of flex items (folders)

If you're creating structures with several foldersflex items, each with its own Insert generator to add issues, ask yourself this question: Can I use a single Insert Generator for the entire structure, and then use a Group generator to organize my issues by a specific field?

Let's see how this can work. If you're using Structure to track upcoming sprints, you could:

Less Optimal Approach

  • Create a

    folder

    flex item for each sprint

  • Add an Insert generator to each

    folder

    flex item, adding issues assigned to that sprint

This approach requires adding several generators, which may lead to slower performance.

Better Approach

  • Add an Insert generator to the top of the structure that adds all the issues you need to track

  • Add a Group generator that groups issues by Sprint

This approach only requires two generators, improving performance. And if you ever need to reassign issues to a different sprint, this approach allows you to drag them from one Sprint group to another!Image Removed

...

Anchor
filter
filter
Be specific with your Insert generators

...

Use a JQL Insert generator and be specific about exactly which issues you want to see. This does the insert and filter all in one step - which will lead to better performance!Image Removed

...

Workarounds for the Insert generator issue limit

...

If you've attempted to build a single structure to be used by several teams or for several different projects, chances are it's quite large, probably requires multiple Insert generators, and maybe even several folders flex items to differentiate between the different teams/projects/etc. For example, you might have a folder flex item for executives, containing all the issues they care about; a folder flex item for each team, with all the issues they need to track; and a folder flex item just for you.

Such structures may take longer to open or feel slow when trying to work in them, and they can be very difficult to navigate or search.

...

As we mentioned above, if you're creating a structure that consists of multiple foldersflex items, each with their own Insert generator, it's better to use a single Insert generator. In some cases, you can use Group generators to accomplish the same things as the folders flex items did. In other cases, you should consider creating more than one structure.

...