In an enterprise environment where Jira is already in production and used every day, deploying any new add-on may initially be disruptive to users.
To ease this transition, we recommend a gradual deployment, as described below.
Start with Champions First
Structure can be limited to a number of users – see Restricting User Access to Structure. The users who do not have access to Structure don't see Structure's footprint in Jira in any way (with one exception, see below).
A common path to gradual deployment is:
- Create a group called structure-users and restrict access to Structure only to that group.
- Add to the group those individuals who initially championed getting Structure for your company and anyone else who actively wants to use it.
- Let them use Structure and spread the word.
- Once it is decided that everybody wants to use Structure, remove these restriction.
- Don't forget to advise everyone to check the Getting Started page.
In the same way, you can gradually enable Structure project-by-project. See Who Has Access to the Structure for details.
Turn Optional Functionality Off
Another way to limit the initial deployment of Structure is to turn off some optional features. Here are a couple of examples:
- Activity Streams. For technical reasons, even if a user does not have access to Structure, they will still see "Structure" as a possible Activity Streams Provider (although they won't see any events coming out of it). If you are initially limiting the number of Structure users, it may be a good idea to remove Structure data from the activity stream.
- Automation. Structure's automation feature can place an additional load on servers, particular as users are first learning to optimize their structures. You can limit the access to Automation by changing permission to access Automation.