This permission allows people to link issues in your project to one another, or to issues in other projects on your site. Jira administrators (anyone with theAdminister Jiraglobal permission) always have access to your project's settings. Only site admins can remove users from your Jira site. Import and export your data to and from Jira Cloud, Common CSV file questions and known issues, Fix error connections between Jira Cloud and Bitbucket, Integrate with self-hosted tools using OAuth, Use AppLinks to link to Atlassian products, Administer projects and links across multiple applications, Assign users to groups, project roles, and applications, Permissions and issue-level security in Free plans, Use manage sprints permission for advanced cases, Customize Jira Service Management permissions, Resolve Jira Service Management permission errors, Add, assign, and delete project categories, Convert a project to a different template or type, Default configurations for Jira Service Management. Migrate between team-managed and company-managed projects, Configure how your board estimates and tracks work. Typically, anyone who can comment on an issue (by having the Add comments permission) should be able to adjust their own comments and correct minor problems like spelling errors or broken links. This permission allows people to alter the time they logged, the time they estimated as remaining, and the description of any work log entry they added to any of your projects issues. For example, if you give someone the permission to Edit issues in a Jira Software project, they still require product access to Jira Software to gain that permission. If you want to allow anonymous access, ask your Jira admin to create a company-managed project for you. This permission allows people to delete any issue in your project, including its associated field data, comments, and work log entries. If you grant a role any of the permissions that appear under the Work on project issues set, anyone with that role can be assigned issues in the project. To add users, groups, or roles to a permission scheme, and grant them project permissions: SelectPermission Schemesto open thePermission Schemespage, which displays a list of all permission schemes in your Jira system and the projects that use each scheme. Configure and manage projects to track team progress. Import and export your data to and from Jira Cloud, Common CSV file questions and known issues, Fix error connections between Jira Cloud and Bitbucket, Integrate with self-hosted tools using OAuth, Use AppLinks to link to Atlassian products, Administer projects and links across multiple applications, Assign users to groups, project roles, and applications, Permissions and issue-level security in Free plans, Use manage sprints permission for advanced cases, Customize Jira Service Management permissions, Resolve Jira Service Management permission errors, Add, assign, and delete project categories, Convert a project to a different template or type, Default configurations for Jira Service Management. Work in Jira Software Cloud team-managed projects. Learn more about Jira Cloud products, features, plans, and migration.
For example, if you have multiple Jira products on the same cloud site, a Jira Service Management agent can be given this set of permissions and collaborate on issues in Jira Software. Typically, these permissions are meant for who you might consider members of the core team. This permission allows people to create a work log entry, where they can indicate the time spent and time remaining to complete the task, including a brief description of the work they did along the way. This permission allows people to add or remove people from an issues watch list. Create projects separate from shared configurations and schemes. Read more about roles. This permission allows people to change the value of the default Reporter field on any of your projects issues.
Learn more about anonymous access. Changing an issues status notifies the issues reporter, assignee, and watchers of the action your team has taken on the task. Limited: When a project is limited, anyone on your Jira site can view and comment on issues in your project. Read more about global permissions. How do single-project and cross-project releases differ? What are issue statuses, priorities, and resolutions? Create and manage issue workflows and issue workflow schemes. A (multi-)group pickercustom field. This permission allows people to change the value of the default Due date field on any of your projects issues. Work in Jira Software Cloud agile projects. Users with this permission can perform most administration tasks, except managing users, importing and exporting data, and editing system email settings.
Private: When a project is private, only Jira admins and people you add to the project can see it in their project directory or its issues in search results. Integrate Jira Cloud with other products and apps. Project administrators manage project permissions for team-managed projects through custom roles. Global permissions are system-wide and are granted to groups of users. What does the progress bar on my roadmap show? This permission allows people to see whos watching any issue in your project. In the Grant permission dialog, select who to grant the permission to and click theGrantbutton. If you add people to a role that grants these permissions, make sure they have product access to Jira Software (for software projects) or Jira Service Management (for service project).
If the permission is assigned through the project role or single user name, it won't be returned. For example, allowing users to create shared objects like filters, or make bulk issue changes. The ability to clarify descriptions and update fields is especially handy for team members who may review tasks during shared rituals like standup meetings, planning meetings, board grooming sessions, or project kick-off meetings. Users with theAdminister Jirapermission can log in at any time but may be restricted depending on their application access. What are issue statuses, priorities, and resolutions?
Read more about custom roles in team-managed projects. Configure and manage projects to track team progress. Give your new scheme a name, and add a short description of the scheme. To view the link properly, they need the same permission in the target project. This permission allows people to alter the time logged, time remaining, and description of any work log entry added by anyone on any of your projects issues.
Users with the Administer Jira permission can always create team-managed projects, even if that group is removed from this permission. Organizations with strict compliance or traceability requirements may consider restricting this permission to keep an accurate historical record throughout the course of an issues lifecycle. Depending on your organization, you might give these permissions to designers, technical writers, consultants, or other supporting roles. For example, for a user to be able to Edit issues in the project, they first must be able to browse the project. Jira admins: Learn how to integrate a development tool with your Jira site. Your Jira admin may limit what you can attach and how big your files can be. The project's access level gives any logged inJira Softwareuser a certain role in your project. You may legitimately want to grant public access to some projects and issues on your site, like in the case of a public bug tracker. Click theActionsdropdown menu and chooseUse a different scheme. They can move any issue through the workflow, triggering any board rules that may be associated with the transition along the way.
Learn more about the difference between company-managed and team-managed projects. Manage and administer team-managed projects, Use Jira Cloud on Apple and Android devices, Use Jira Cloud with other Atlassian products, Integrate Jira Cloud with Microsoft Teams, Start a new software project for your team, Learn how company-managed and team-managed projects differ.
Control who has access to your Jira Cloud products and give them the right permissions to perform their role. You can find it in your list of permission schemes with the name Copy of
For example, in a Jira site where anybody can sign up and create issues, a user with this permission and theAdd Commentsproject permission could comment onallaccessible issues. This permission allows people to view any issues underlying workflow and update the status of any of your projects issues. ThePermission Schemespage opens. How can I track progress of my projects in Jira? Read the details of each available project permission. This permission allows people to remove any file or image they attached to any issue in your project. Its a bit of a superpower. Team-managed software projects have three, simple access levels: Open: When a project is open, anyone on your Jira site can view, create and edit issues in your project. Copying a permission scheme gives you this quick start to tweak a scheme and meet the requirements for a new project. edit other peoples access to the project, enable and disable agile features like the roadmap or sprints, delete a service project and its issues outright. Your projects permissions are updated and the project now follows your permission scheme. Once a permission scheme is set up, it can be applied to all projects that have the same type of access requirements. This practice can help clarify work if people leave erroneous or inaccurate comments. You can't delete thedefault permission scheme. Open organizations can benefit from allowing anyone to create issues in your project. Typically, adjusting other peoples work log entries is a permission reserved for team leaders or other management roles. Explore issues, issue types, issue custom fields, issue screens, custom field context, and issue field configurations in Jira Cloud. How are usernames changing in Jira Cloud? Jira will recreate this permission scheme if you create a new company-managed software project, and associate it to your new project. This permission is called Work On Issues in company-managed projects. Typically, people who actively work and log time in your project will need to adjust their own work logs in case of data entry errors or changes to the works scope or requirements. Typically, any team member or collaborator needs this permission. Learn how to set up Jira Software Cloud and integrate it with other products and applications. This permission is a combination of the Transition Issues, Resolve Issues, and Close Issues permissions in company-managed projects. Every company-managed project has apermission scheme. Learn how to set up, customize, and manage Jira Cloud projects. Manage users, groups, permissions, and roles in Jira Cloud. Open organizations encourage teams to edit each others comments to correct minor problems like spelling errors or broken links, and generally keep the communication stream clean. This displays theGrant permissiondialog. While some teams may reserve this permission for management roles, open organizations can benefit from granting this power to autonomous team members.
For example, they may find and report bugs when using your teams products. Read more about project roles in Jira. Control who has access to your Jira Cloud products and give them the right permissions to perform their role. Enable and disable the progress monitor in your project, Change color of issue schedule bars on your roadmap, Change how many completed issues show on your timeline, Add your roadmap to a Confluence Cloud page, Troubleshoot the roadmap for company-managed projects, Troubleshoot the roadmaps for team-managed projects, Manage insights in a company-managed project, Understand backlog insights in company-managed projects, Understand insights on the board in company-managed projects, Construct cron expressions for a filter subscription, Use advanced search with Jira Query Language (JQL). Organizations with strict compliance or traceability requirements may reserve this permission for team leaders or project managers. Were currently working to decouple these permissions. The Jira admin helper can help you find out why a user can or can't see a certain issue. Read more about managing groups. What is the Dependencies report in Advanced Roadmaps? Go to Cloud Automation documentation | Why did we do this?
What is advanced searching in Jira Cloud? Add, edit, and delete a field configuration scheme, Use workflow triggers for company-managed projects, Use workflow validators with custom fields, Use workflow validators for company-managed projects, Add, edit, and delete an issue workflow scheme, Customize the layout and design of Jira applications, Configure the look and feel of Jira applications, Create links in the application navigator, Configure Jira Cloud to send emails on behalf of your domain, Configure email notifications for a custom event, Manage DMARC authentication for incoming emails, Grant global permissions to a group of users, Revoke global permissions from a group of users, Troubleshoot permissions with the Jira admin helper.
You can grant the global permissions described above to user groups. Locate the permission scheme you would like to update, and selectPermissionsin theActionscolumn to view the scheme. You can give specific access or additional permissions to individual people by creating your own project roles. All content related to Jira Cloud Automation, previously under the Automate your Jira processes and workflows section, have moved to the new Cloud Automation docs. For example, if the issue requires images from a designer to help describe the work, it might be beneficial for team members to keep attachments up to date, even if they arent the owner of the original attachment. In company-managed software projects, Jira admins can control who can be assigned an issue using permission schemes. Learn more about sprints, Scrum, and how to practice agile methods in Jira Software. Anyone, which can make issues public to the internet. Configure columns and statuses in your team-managed project, Assign statuses and edit columns in a team-managed project, Manage columns and statuses in team-managed projects, View and understand insights in team-managed projects, Understand insights on the backlog in team-managed projects, Understand insights on the board in a team-managed project, Common Jira Software configurations for Advanced Roadmaps, Change your Advanced Roadmaps plan settings, How Advanced Roadmaps shows issues on your timeline. This permission allows people to attach files to any issue in your project. In these cases, a project becomes visible to any logged in user on your Jira site.
Theres a known issue when granting aUser custom field value,Reporter,Current assignee, orGroup custom field valuetheBrowse Projectpermission. Your newly added scheme appears on the Permission Schemes page, but its an empty vessel.
Organizations with strict compliance or traceability requirements may reserve this permission for team leaders or project managers. Or, for a user to be able to resolve an issue, they must also be able totransition the issue. Integrate Jira Cloud with Confluence, development tools, apps, and self-hosted tools using OAuth and feature flags. You can grant permissions to: Individual users, which your site admin can invite to your Jira products. the difference between company-managed and team-managed projects.
Learn more about project roles. This permission allows people to remove any work log entry added by anyone on any of your projects issues. How can I find and resume work using the navigation bar? Project permissions are managed in two ways: Jira administrators manage project permissions for company-managed projects through permission schemes. Configure statuses, resolutions, and priorities, Translate resolutions, priorities, statuses, and issue types, Add, edit, and delete an issue type scheme, Custom fields types in company-managed projects, Add, edit, and delete a field configuration, Associate field behavior with an issue type. Configure issues to track individual pieces of work. SelectPermissionsfrom the sidebar. This set of permissions is typically granted to developers, product managers, designers, quality assurance engineers, and others directly working to accomplish your projects goals. Typically, removing other peoples work log entries is a permission reserved for team leaders or other management roles. Click theAssociatebutton to associate the project with the permission scheme. Users with this permission can see the names of all users and groups on your site. You must be a Jira admin to use the permission helper. Configure statuses, resolutions, and priorities, Translate resolutions, priorities, statuses, and issue types, Add, edit, and delete an issue type scheme, Custom fields types in company-managed projects, Add, edit, and delete a field configuration, Associate field behavior with an issue type. Create and manage issue workflows and issue workflow schemes. Select Add Permission Scheme. Your projects access level sets general permissions for people across you Jira site. Find out more about how project permissions work in Free plans. We recommend assigning permissions through project roles, rather than individual users or group access. You can't edit project permissions or roles on the Free plan for Jira Software or Jira Work Management, and you can't configure issue-level security on any Free plan (including Jira Service Management). Site admins can grant this permissionin user management. When you add someone to a role, remember that they also inherit the role permissions given by your projects access level: In Open projects, everyone on your Jira site is given the default Member role. Show or hide releases on your project roadmap.
Some teams may restrict this permission to the core members of a team to keep their backlog tidy. Granting permission to make bulk changes may be risky.
This set of permissions is typically granted to team members who dont play a central role in your project.
For that reason, you may reserve this permission for team leaders, human resource managers, or other management roles. Typically, anyone who can attach files to an issue (by having the Add attachments permission) should be able to remove their own attachments. What do the symbols in Advanced Roadmaps mean? Some project permissions are only usable if your users also have access to the Atlassian product that checks the permission. In Limited projects, everyone on your Jira site is given the default Viewer role. For each permissions available, select theEditlink to grant the permission to a user, group, or role. Open organizations encourage teams to keep each others work up to date by adjusting fields when viewing tasks throughout the course of their work. Share dashboards and filters with other users. In theActionscolumn, click theCopylink for the scheme that you want to copy. Learn more on how you can set up Jira Cloud for your team.
This can either be an actual group picker custom field, or a (multi-)select-list whose values are group names.
This practice can help clarify work where many versions of a file or image are uploaded throughout the course of working on the issue. Only your site admin can grant individuals product access. Select the permission you want to grant in thePermissiondropdown. Scroll to the bottom of the page to find theAdd Permissionsection. Removing this permission does not delete existing team-managed projects. From the sidebar, selectPermission Schemes. Learn more inviting users. What are partial rollups in Advanced Roadmaps? Show or hide dependencies on your roadmap, Create or remove dependencies on your roadmap. Any updates you make the scheme or its grants apply immediately to the project associated with the scheme. What are the different types of activity on an issue?
What about the assignable user permission? Integrate your issues and development tools, Reference issues in your development work, View development information for an issue, Search for an existing or shared dashboard, Learn about changes coming to your Jira Cloud experience, Upcoming changes: Epic link data above the epic level, Upcoming changes: 'epic-link' replaced with 'parent'. Read the details of each available project permission. This makes it easy for Jira admins to manage the permissions of many projects at once, without having to adjust each projects settings individually. It displays a list of all the permission schemes in your Jira site and the projects that use each scheme. How can I plan with releases on my project roadmap? For traceability and historical investigations, we recommend preserving all issue comments. This permission is typically reserved for team leaders or project management roles. This includes adjusting the sprint duration and goal. To use the scheme properly, you need to: Add users, groups, and roles to the scheme and grant their project permissions.
For a project's access level, you'll need access to the Jira site. You may grant this permission to anyone logged in to your Jira site.
Learn more about Jira Cloud products, features, plans, and migration. Once you have your project permission grants figured out, you can put the scheme into effect by associating it with the projects its meant to govern.