Page tree

You are viewing documentation for Structure Server and Data Center version 5.5 and patch releases. For other versions, see Version Index or Structure Cloud.

Skip to end of metadata
Go to start of metadata

When introducing Structure in an organization it may make sense to limit the use of it to a pilot project or some specific group of users. This can be done via Structure Administration page (Administration | Structure).

On this page you can configure the following:

  • Projects with Structure. You can enable structure for all projects or you can limit its exposure to a number of specific projects. If Structure is not enabled for a certain project, issues from this project cannot be added to structures and users, who only have access to such projects will not see Structure at all.

    If you create a new project in Jira, which should be using Structure, don't forget to add it to the list of enabled projects (unless you have selected the All Projects option).

  • Users of Structure. You can define which users have access to Structure (on top of the restrictions by projects). You can use Jira Groups and Project Roles.

    When Structure is enabled for anyone, even anonymous visitors will have access to Structure. It means that even if they don't have access to projects and will not see any issues in a structure, they will still see the structure name and may see the Automation settings. To make Structure accessible to only logged in users, restrict access to jira-users group.

  • Users who can create structures. By default, any logged-in user with access to Structure can create new structures of their own. Using this setting you can restrict this permission.

  • Permission to create Synchronizers. By default, any logged-in user with Control access level for a particular structure can manage Synchronizers of that structure. Using this setting you can restrict this permission.

    Synchronizers were a mechanism for building self-updating structures in older versions of Structure (pre 3.0). In version 3.0 Automation was introduced to replace them and synchronizers are gradually faded out. Starting with version 5.0, synchronizers functionality is not visible anymore if there were no synchronizers installed on the instance previously. To access it, you'll need to enable it as described here.

    If you do see them on your instance, it might be best to restrict this permission to admins only to prevent users from creating new ones ones and encourage the use of Automation instead.

  • Permission to manage Automation settings. By default, any user with Edit Generators access level for a structure can add and configure generators. Unlike synchronizers, generators cannot cause any unexpected changes to Jira data (see Synchronizers vs Automation section), so from this point of view, it's safe to let users work with them. One thing you need to keep in mind though, is that they can start affecting the server performance if they are used to build very large structures (see Performance Considerations section). This is especially important in large instances. In version 4.6 we introduced the Automation Timeout mechanism, which will stop generation process if it's taking longer than a certain period time, but it still may make sense to introduce the Automation feature gradually. A good practice could be to identify some power users, who can start using it straight away and then organize some use case based training or create instructions for less experienced users.
  • No labels