Skip to main content
Skip table of contents

Project Milestones Settings

The Project Milestones settings are only accessible by Jira system administrators

How to access the Project Milestones settings?

As Jira system administrator, you find the app settings via Apps → Manage Apps → Project Milestones settings on the left sidebar.

What can you do in the settings?

The admin settings empower system administrators to adjust configurations for:

  • Permissions that dictate who can view or edit milestones in projects, based on project roles, user groups, or individual users.

  • The fields designated for automated milestone mapping, applicable both globally and on a per-project basis.

Permissions

By default, there are no restrictions in place, allowing all Jira users and groups to access and utilize the app freely.

image-20241218-153018.png

Default - no permission restrictions defined

Activating the toggle allows you to limit access to the app for specific projects, user groups, or individual users. You can configure view and edit permissions independently. Users who lack view permissions will encounter the following message when attempting to access the app, whether from the project page or the global project overview.

No_app_access.png

No access message

By Project

To manage your projects effectively, you can select a project from the top menu to add it to your list and establish permissions for that specific project. Once the project is added, you have the option to assign project roles, user groups, or individual users, allowing you to customize view and edit permissions exclusively for them.

image-20241218-153609.png

Permissions set for projects

In the example provided, all users and groups associated with the ‘Demo Project’ have access to the milestones, although they cannot make any edits. Conversely, in the ‘Demo Kanban Project,’ the app is accessible only to members of the ‘Member’ project role and to the individual user, Mark Sanders. Additionally, in this project, the milestones are set to read-only, preventing any modifications.

By Project Role

Permissions can also be defined by project role, similar to how they are assigned for projects.

image-20241218-154005.png

Permissions set for project role

Access to project milestones is restricted solely to members assigned the ‘Administrator’ project role. These members have the ability not only to edit existing milestones but also to create new ones.

By Group

To add a group to the list and grant app permissions, simply select the desired group from the options at the top.

image-20241218-154247.png

Permissions set for user group

By User

Permissions can also be assigned to individual users, just as they are for groups.

It is important to understand that user settings will always take precedence over project, project role, and group settings. This means that a user with specific permissions defined here will retain those permissions across all projects, regardless of whether they are a member of a group or assigned a project role.

Save settings

You can easily discard your modifications at any time by clicking the cancel button. If you wish to save your settings, simply press the save button. Your modifications will be clearly displayed in the dialog that appears.

image-20241218-154519.png

Summary of changes to app permissions

When you click on save on this dialog, the settings will be applied. A flag shows up, when it has been saved successfully.

Field settings

The field settings enable you to modify the date field utilized for automated issue mapping to milestones. By default, the global setting employs the due date field for this purpose. However, you have the flexibility to change this field within the settings and even assign specific date fields for each project.

image-20241218-155249.png

Field settings - globally and per project

In this example, the due date field remains configured as a global field for issue mapping. However, in the ‘Demo Kanban Project,’ the target end field has been utilized instead.

Please be aware that project-specific settings are only available for company-managed projects.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.