Think about user personas when setting up dashboards and filters. You can also set up dashboards for the management team to keep track of their projects. You can share these filters and dashboards with necessary groups, or a given project to help these users find their work faster. Learn about your different user groups and create dashboards for them. Depending on the user, each person might want a specific dashboard or they might be happy with the one you create for them. One of the great features of Jira is that anyone with access can create a filter or dashboard.

Once the tedious business analysis is done, you will reap the benefits of reduced administration time (for configuration tasks) and have consistency across projects for your users. It is especially important to define your process before getting started with your projects. Alternatively, creating projects without shared configurations could create many one-off workflow schemes, permission schemes, and issue type schemes.

Each project can have different workflows associated with different issue types. In doing so will help the organization scale as it grows It will be easier for admins to configure projects, new users onboard to new projects, and current users to understand the work process for each project. Once this is completed, you are ready to associate your workflow with the right issue types and start creating issues.ДЇor small organizations with a minimal number of projects, itвЂ™s best to apply shared configurations and a strong governance process for the team. Think through normal cases and edge cases to thoroughly understand how your team gets work done. Before you begin creating issues in a new project or Jira instance, take time to consider all the aspects you want to include in your workflow. Your workflow is something that should be thought through with proper iterations. From an administrative perspective, it will be easier to allow access at a later time instead of revoking access.ДЄs will be discussed in our upcomingВ Default Anti-patterns in Jira blog, the default Jira workflow isnвЂ™t a one-size-fits-all solution for your projectвЂ™s workflows. If you assign groups to different roles then you might be able to reuse a permission scheme (like the Perfect Permission Scheme) that grants access through roles. We recommend applying the permissions in groups, then assign roles within the project if necessary. However, does the product management team need to see it? Absolutely. For example вЂ“ If there is a marketing project in Jira, does the HR team need to see it? Probably not. While Atlassian advocates for an open working environment (this is the default permissions scheme), it will be more beneficial to only grant permissions to groups that need them. If you find yourself only putting one person in a group, then the group is not necessary. You can have an unlimited number of groups in your Jira instance, but try not to get too granular with your groups. If someone works across multiple departments, you can put them in multiple groups. Put all of the people from different departments into different groups. As an overall rule of thumb, follow the organizational structure of your company. If you are using Cloud, check out Atlassian Access. How do you determine which users go into which group?Дo you already have an LDAP set up with other systems? If you are deploying Jira Server, it will be useful to integrate this LDAP with your instance so that Jira imitates your other systems in terms of user management. This lays the foundation and makes it easy to create new projects and spaces by simply giving permission to the group that needs to see the content displayed in the project. In order to reduce the time and effort spent to manage users, we recommend placing similar users into groups in your user management section of your instance. Managing users in big organizations can become a full-time job in and of itself.

Jira client atlassian tutorial pdf