Overview of Jira Admin

Jira administration administrates the jira account and jira administration has divided into two sections as Atlassian Admin and Site Jira Settings, as soon as you logged into your jira account by using your login credentials, you will see a settings icon on the left down corner, just click on it, you will see the two different parts of the Administration.

Basic Search

Atlassian Admin

Atlassian admin contains the two parts such as user management and Billing.

User Management:

User management allows us to create a user account and assign them to the user, you have an option called invite user, you can invite them by sending a signup URL.

Just click on the invite user and then it will ask you to enter the user email address, enter the required paths and click on the invite user, in the below image I invited the one user

And at the bottom of the user page, you will see the status of the user as shown below.
The same way you can also export the user from the selected groups as you required, just click on the export user then it will ask to select the users from the users status and also by using the Additional data and then click on the download file.


In the Billing part, you can update the billing details, billing history, billing estimation and also you can manage the subscriptions, the Billing page will look like below.

Jira Dashboards

Jira Settings

Jira Settings is divided into Five parts as

  • System
  • Products
  • Projects
  • Issues
  • Apps


In the system sections, you can make some settings in the General settings and Advanced settings and also you can edit the settings by clicking on the Edit Settings.


Products have two parts in it as Product access and Administration access and we can view and configure which group provide access to your products.

In the product access, we can add the new group to it and also we can edit the current group and if you do not require any group then you can delete the group as well.

Any user added to a group with product access will count your product license and when a user is granted access to a product, they will be added to the products default access group and also the groups used administration access cannot be set as a default access group.

Next, we have Administration access, in that the groups in jira administration do not count towards your product license, so when you want these groups to use jira, you need to grant them product access.


Again the Project contains the two parts as projects and project categories under the jira settings if you click on the projects it will show you the current projects which are present in your jira account and also here you can make settings to the current project.

Also, you can create a new project here.

Project Categories:

Project categories show that different types of projects categorized based on their names, you can also create a new project category.


Issues will show you the different types of issues and different issue schemes and it also contains subtasks.

Issue type page


An issue type scheme determines which issue types will be available to a set of projects, it also allows to specify the order in which the issue types are presented in the user interface. Below image represents the Issue type scheme page

Sub-Task page


apps sections provide us with finding the new apps to integrate with Jira software and under the manage apps, we can install, update, enable, and disable the apps here.
Find New Apps page


Manage Apps


Jira Project Flow

Creating a new user in Jira

In the previous section, I briefly explained to you about the Jira administration and admin settings, now let us create a new user and make some options over here.

Go to user management, it will open an invite user page, so let us invite some new user.

In the above image, you will some details about the new user as username, status, and actions, etc.. just click on any of the user accounts, it will display some details such as email address, access, roles, and groups.

You can observe one more thing that, any user who wants to access the jira account is automatically assigned with the group as jira-software-users.

one more interesting thing here is you can log in as a user because jira will create a jira-software-user group as the default group.

Agile Methods

Creating Groups

A number of things or a number of people with similar characteristics/properties are gathered together is called a group, same way we can also create a group of users with similar kind of work and instead of giving the admin access to the individual we can give it to the group itself.

By clicking on groups under user management the group will look like below

Clicking on the create group and enter the required paths, I created a group called tester, once you created the group.

Next, jira will ask you to add the group members, so add the members from the user list and click on Add.


If you added members successfully to the group then the page will look below.

You can see the list of different kind of groups as below.

Principles of Agile Methodology

Handling Global Access and Use Cases

Global Permissions:

There are two types of permissions in Jira one is Global permission that it applies to irrespective of projects and another one is a project role which varies from project to project and we can configure it for each and every project.

Let us discuss Global permission, clicking on the system under jira settings take you to the Global permission section.

You can see in the description it is mentioned that these permissions are applied to all the projects, here we have Jira permissions, browser user and groups, share dashboards and filters, manage group filter subscription, etc...

Associate Project to an Issue

In the previous sections, you learned how to create an issue and also know how to create a project, now let us know how to associate these issues to the project.

For this, if you want to create another new project means you can create or you want to associate it to the current project means you can do it.

So here I am going to create a new scrum project and also I am creating some issues and epics as well as versions and then assigning these issues to the newly created sprint.

So I created a new project called scrum demo project

Next, I am creating some issues in the Backlog

Creating an epic called Demo

No, I am going to create a version with the version v1.12 and assigning some issues to the version as well as to the epic and after that creating newsprint. If you have created the version and epic successfully then the backlog page will look like below.

So I assigned some issues to the sprint and hence you will see the page as below and then click on start sprint.

So we have successfully created the sprint and you can see there are Four issues are In Progress and three are Done, so let us complete this sprint.

Now, let us create an issue called improvement, go the issue type and click on the add issue type


Now, just go to issue type scheme and you can see that for every project, jira assigned a scheme but you can observe that our newly created project scrum demo project has not assigned with the improvement issue.

So we need to assign the improvement issue to the scrum demo project, for that you just click on the edit which is present in front of the issue type scheme, jira will take you to the modify Issue type scheme page, where you can just drag and drop the new available issue to the currently available issues table and click on the save.

If you added a new issue successfully, then your issue type scheme page will look like below.

Converting An Issue into Subtask

Creating a Screen for Issues Types

Screen: A screen is an arrangement of fields that are displayed when the issue is created, edited or transitioned through the workflow.

To choose screens that are displayed when issues are created or edited please map the screens to issue operations using Screen Schemes.

To select which screen is displayed for a particular workflow transition, please select the workflow the transition belongs to and edit it.

Note: it is only possible to delete a screen if it is not part of a Screen Scheme and is not used in any workflows.

The issue types which we have created, we do not assign them any screen to it and jira is opening them in the default screen of all the issue types.

In this section as a user, I want to have the screen for newly created issue type, as you know in the previous sections we have created an issue and associated it with the project. the improvement issue does not need the soo many values to display and hence we can set the required values to it and develop a screen for improvement issue.

by clicking on issues under jira settings, you will see a screen tab just click on its screens and it will display you view screens page, here you can search for the screen, and also there will be a list of current screens such default screen, KSP screen, resolve issue screen, SDP screen SSP screen, etc..

clicking the on the Add Screen, you are going to add the screen for the issue and then give a name to it and then click on ADD.


Once you add a screen, you need to configure the screen, that means you need to configure what values you want to display on the screen.

Here In the Fields tab, I want to see Assignee, description, Resolution, Reporter, and summary and if you create an issue and if you select the improvement then it shows you above values.

If you have successfully created the screen then you will see as below in the screen page.


And we know that all the activities would be handled through a scheme and hence we have to create a new issue scheme, here I created a new screen scheme as LR-improvement scheme and selected the default screen as scrum demo improvement and then click on Add


So we have created the scheme for the new issue, now we have to make a set of all the schemes we have in our project, so just click on the Add type screen scheme and enter the name of the scheme as LR-issue type scheme and select the screen scheme as the default screen scheme and then click on Add


Next, configure it with issues as shown below

associate-an-issue-type-with-a screen-scheme

Next, go to issue type screen scheme, you will the screen which you have created and the project as scrum demo project so next we need to integrate it with the project.


Integrate the new generated scheme to the project, so just go to the project and then select the new scrum demo project under this go to project settings and then select the screens, so it is currently using the scrum issue type screen scheme.

So just click on the actions and select the use a different scheme.


Now, associate scrum demo issue type scheme with the project and then click on the associate.


If I go to create and select the scrum demo project and issue type as improvement then it will display the values only description, assignee, summary and report