Anyone with the "Create Issue" permission in a specific Jira project can create issues, which is controlled by project administrators through Permission Schemes, allowing roles like developers, BAs, or even anonymous users (via widgets/APIs) to create tickets, though teams often set specific guidelines for who should create what.
JIRA 5.0 and later. The Rest API allows you to create an issue. The JIRA REST api allows you to easily create an issue. You can POST a single JSON document.
Only Jira administrators can create company managed projects. However, as you correctly stated, there is the global permission of granting users the ability to create their own team managed projects.
Users are assigned space roles, and these roles are used in permission schemes to assign permissions to a user. These schemes are then leveraged by several spaces to administer their permissions. Multiple users can be assigned to a role, but similarly, multiple roles can be assigned to a user.
If you're an admin and are on a Company-managed Jira project, you can create a Jira Component. To add components to your Jira project, follow these steps: Go to Project Settings.
4 answers
A board's administrator is the only person who can change the configuration of a board along with JIRA administrator users. By default, the administrator of a board includes the person who created it.
In my understanding, Jira admins typically:
While the project manager ensures every team member contributes to project progress, the project administrator is in charge of tracking individual tasks. Project administrators look closely at the project schedule and get task-level updates from team members on each task.
From the sidebar, select the work type that you want to restrict access to. Choose the lock icon at the top-right of the work type. Select the roles that can view new work items by default from the dropdown. Select Restrict.
The workflow editor is a graphical tool that allows you to create, visualize, and edit the steps and transitions of a workflow. You will need to log in as a user with the 'Jira System Administrators' global permission to access this functionality.
If you are not Admin, then you don't have access for creating project and you can contact your jira Administrator and ask for help. If you are an Admin, then in project settings check your Browse-Administrative-Project permission and grant it to yourself.
Project administrators assign members to project roles specifically for their project(s). A project administrator is someone who has the project-specific 'Administer Project' permission, but not necessarily the global 'Jira Administrator' permission.
As a JIRA developer, you develop and maintain automation workflows, develop plugins to extend JIRA capabilities, build dashboards for JIRA Connect add-ons, configure custom fields, create custom preset filters, test outcomes, and identify defects.
An alert created by a Jira Service Management integration has a level of importance, which is defined as its priority level. An alert may have one of the five different types of priority levels: P1, P2, P3, P4, and P5 where P1 indicates the highest priority and P5 is the least. You can set the priority manually.
Titles Reflecting Varying Levels of Responsibility
A title that points to higher responsibility than a standard Project Manager is often the “Senior Project Manager” or even the term “Project Director”. Individuals with these titles typically shoulder broader organizational or strategic responsibilities.
Yes! If you're looking to take on the added pressure and challenges associated with projects, the techniques of project management for administrative professionals will give you the confidence you need to get the job done.
A manager is a hired employee with limited authority. While at a lower level than administrators, managers are generally higher than other employees but still face competition.
There's no specific path you must follow to become a Jira administrator, and there's no particular course to take or certification to achieve. But the following skills and experience are great adds to any Jira administrator's resume: Obtaining a degree in computer science, IT, or a related field.
Frequently asked questions about JIRA Administrator salaries
However, the typical pay range in India is between ₹6,24,250 (25th percentile) and ₹10,92,500 (75th percentile) annually. Salary estimates are based on 95 salaries submitted anonymously to Glassdoor by JIRA Administrator employees in India as of January 2026.
Log in to your Jira Cloud instance. Click on the settings cog icon in the top right corner. If you see options like "User management" or "System," you likely have Jira administrator permissions.
A Jira administrator is a user with the Jira administrators global permission. A project administrator is a user with the Administer projects project permission for a particular project. By default, the Administer projects permission is assigned to the administrators group through the Administrators role for projects.
You already have some experience with JIRA Administration but want to take it a step further and become an Accredited administrator. Each of these 3 steps takes around 40-60 hours + two exams to pass.
Jira's default hierarchy (epic > story > sub-task) can limit flexibility, as sub-tasks cannot be added to sprints. Workarounds like using Jira Cloud Premium offer more levels (feature > epic > story), but they come with significant costs and still prevent the addition of epics directly to sprints.