Project Configuration

Project Configuration

By setting up project configuration, admin can enable or disable various sharing options and define what information external users can view or edit. You can also manage security settings when creating an external share link.

How to Navigate

1. Go to the Apps menu in the left-side panel of Jira.

2. Click on External Share.

3. Navigate to the Project Configuration tab.

Open

Multiple Configuration Presets

When viewing the Project Configuration tab for the first time, you can see that there is a default configuration already set up. The default settings can be edited and will be applied to all projects in the instance.

You can also create exceptions by setting up custom configuration presets for specific projects. This allows you to apply different rules where needed.

• Default Project Configuration: Applies to all projects. (Enable/Disable)

• Custom Project Configuration: Can be assigned to one or more individual projects.

Open

Default Project Configuration

 

Open

Custom Project Configuration

Enable or disable External Share

You can disable External Share for an entire project using the configuration settings.

This is particularly useful for private projects (e.g., for the HR team) that must not generate any External Share links. It allows you to secure a project temporarily without losing existing link data.

Open

Open

• If External Share is disabled, all existing links in that project will also be disabled but not deleted.

• When users try to access a disabled link, they will see an error message like the above image.

• If External Share is later re-enabled for the project, all previously created links will become active again.

Project Configuration Options

General tab

Use this tab to control which features are enabled in shared links. You can toggle the visibility or access for:

• Issue Creation: Allow issue (work item) creation on board, filter, and timeline shares.

• Voting

• Fields Configuration:

  • When enabled: Only fields defined in this configuration are allowed on shared issues (work items).

  • When disabled: Fields outside the list are also allowed on shared issues with all permissions.

Open

For each enabled field, you can grant external users permission to view, edit, or add content:

• Labels (View / Edit)

• Status (View / Edit)

• Comment (View / Edit)

• Created (View / Edit)

• Due date (View / Edit)

• Summary (View / Edit)

• Updated (View / Edit)

• Assignee (View / Edit)

• Priority (View / Edit)

• Reporter (View / Edit)

• Sub-tasks (View / View content)

• Affects versions (View / Edit)

• Attachment (View / Add)

• Components (View / Edit)

• Linked Issues (View / View content)

• Description (View / Edit)

• Fix versions (View / Edit)

• Weblinks (View)

• Worklog (View)

• Time tracking (View / Edit)

• Approval (View)

• Changelog (View)

• Internal Comments (View / Add)

• Checklist for Jira (View)

• Smart Checklist (View)

• Original estimate (View / Edit)

• Public Attachments (Add)

Admins can select additional fields by searching from the drop-down menu.

Security tab

The Security tab allows you to configure link security settings, such as:

• Link Expiration date: Set a required or optional expiration date and time.

• Password Protection: Allow or require a password for link access. Default length is 12 characters, but you can set a custom value.

• Public Link: Allow or Disable, On/Off

• Display Comments with Restrictions: Allow or Disable, On/Off

• Corporate SSO Login: Allowed, Required, or Disabled. You can also add an SSO Profile (see the SAML/SSO Setup Guide).

• Selected Users: Allow or require access for specific email addresses or domains.

• Defining the pool of accessible users:

  • All users (default off)

  • From share (default on)

    • Users visible in the share. If there are issues, this also includes users associated with the ticket through fields such as comment authors or mentions in rich-text areas like description, environment, or comments

    • Selected users (Multi-select, default off)

• Fallback actor: When enabled, the system can automatically switch to a specified actor if the current one does not have permission. If the fallback actor is missing or also lacks permission, the share will be disabled.

• Limit shared issues only to current project: If it's enabled, only issues from the current project are shown on Board, Filter, and Timeline shares

Open

 

Open

 

Issue Fields tab

In this tab, you can:

• Define the default state of various options when a new share is created.

• Customize default share names

  • You may redefine default names of shared issues (work items), boards, filters and timelines. Using names of contextual fields will results in substituting them with actual values. Available fields:

    • ${userName} - name of the share's creator'

    • ${userMail} - mail of the share's creator

    • ${creationDate} - date in dd/MM/yyyy format

    • ${creationUSDate} - date in MM/dd/yyyy format

    • ${creationTime} - time and date in dd/MM/yyyy HH:mm format

    • ${creationUSTime} - time and date in MM/dd/yyyy HH:mm format

    For Issue shares you may use additional fields:

    • ${issueKey} - key of the issue

    • ${issueSummary} - summary of the issue

    • ${issueParent} - parent of the issue (if exists)

Open

 

Open

 

Filter Fields tab

Control which fields are visible in the shared Filter view.

• Toggle: Only fields defined in this configuration are allowed on shared filters.

• Toggle: Summary and description search box is shown by default (or hidden if disabled).

Open

Filter fields:

• Labels

• Status

• Created

• Due date

• Project

• Summary

• Updated

• Key

• Reporter

• Priority

• Assignee

• Time tracking

• Fix versions

• Custom fields

Audit tab

The Audit tab provides a record of configuration changes. It shows:

• When the project configuration was created

• Who created/updated it

• The date and time of the last update

Open