Skip to main content
Skip table of contents

Global configuration

General settings

Keep in mind that the global settings are only available for Jira admins so if you’re a user and want to customize the Epic Sum Up global settings, please refer to your Jira admin.

Summary Panel

First, ensure all issue types you wish to configure are added to the “Issue types with Summary Panel”


Admins can also limit the access to the Summary Panel and Time Sheet.

Summary Panel

Please note that each level of configuration will override the previous ones. 

The hierarchy of the Summary Panel configuration is as follows:

  1. Summary Panel global settings

  2. Summary Panel global settings per issue type(s)

  3. Summary Panel project settings

  4. Individual issue configuration

Now that you understand how all the configurations on Epic Sum Up work, you can begin customizing your Epic Sum Up Summary Panels to the needs of your business.

1. Global settings

Admins can configure the Summary Panel to show different metrics, depending on the company requirements and preferences. Once this is configured, it will be used as your standard configuratio for Summary Panels. You can also customize the Summary Panel configuration on a local project basis, which you can learn more about here.

2. Global Settings per issue type(s)

Provided that you have added all the issue types to the general settings you can customize the Summary Panel global settings for each issue type, individually.

There are no limitations to how many Summary Panels can be configured. Admins can select the issue types to display to the Summary Panels. 

All configurations at this level will override the global Summary Panel configuration.

For configuration options of progress bars, you can have a look at this page.


1.Define issue types as containers

Define which issue types can be used as containers. Only the issue types set here can become a container parent to other issues or containers. 

2.Define which link types to use

You can choose which link type or types users should use to create container structures. 

Let’s take a look at how users can use this, using the example links: Container Parent and Container Child. 

The link name refers to what the linked issue is in relation to the issue you are viewing. So if you are using the container parent link, the linked issue will become a parent of the issue you are viewing. And if you are using the container child link, the linked issue will become the child of the issue you are viewing. 

You can also switch the direction of the links to have it the other way around. Or allow users to use multiple types of links. 

Which link types are used for building containers is currently only viewable in the global configuration. As users can’t access this configuration, it is up to the administrator to let users know which link types to use. We are currently working on implementing a solution for users.

JavaScript errors detected

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

If this problem persists, please contact our support.