--- version: "v4.1.0" language: "en" --- # Smart Panel for Jira Cloud ## Documentation * ### [Installation Guide](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/installation-guide.md) ### [Administrator Guide](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/administrator-guide.md) * ### [Project Administrator Guide](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/project-administrator-guide.md) ### [User Guide](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/user-guide.md) * ### [Release Notes](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/release-notes.md) ### [FAQ \& Support](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/faq-support.md) * ### [Migrate Smart Panel from Data Center to Cloud](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/migrate-smart-panel-from-data-center-to-cloud.md) --- version: "v4.1.0" language: "en" --- # Administrator Guide ![Administrator-Guide.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_7df7396a4df3e2c6cb5d270a9cff8de21111fe2945e5abe37a211e4f0ec07de2/Administrator-Guide.png?cb=7e54230d43b5119c561c7ccb39888248) ## This guide includes information on: * [Smart Issue Panels for Jira](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/smart-issue-panels-for-jira.md) * [Smart Wiki Panels for Jira](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/smart-wiki-panels-for-jira.md) * [Example Smart Issue Panel](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/example-smart-issue-panel.md) * [Smart Values in Smart Panels](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/smart-values-in-smart-panels.md) --- version: "v4.1.0" language: "en" --- # Date Format Consistent with User Settings The date format for both the Issue Panel and the Wiki Panel aligns with the user-defined settings in Jira. Step to configure data format: 1. In Jira, go to **Administration** (cog icon), choose **System** (Jira admin settings) 2. In **General configuration** , choose **Advanced Settings** (on the top-right corner) ![image-20260130-084704.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_80b87ffdcc8dcc6421072c57978c3fa4e5c2d36564032a8a2fbf197570a6fbf2/image-20260130-084704.png?cb=c37974f8ef8beb6b7be6f94f1152a2a3) 3. In table, find the keys below to update date format - `jira.date.time.picker.java.format` - `jira.date.time.picker.javascript.format` ![image-20260130-085007.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_bd49effaa3d47d320e78a346934bdaa18db161b792c848f72510a450a44e69a8/image-20260130-085007.png?cb=a69dddedeb8cb2039b4913581d33048a) Date formats in the panel are synchronized in **Smart Panels** ![image-2026-01-07-17-41-44-973.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_3510e6f468dba228be3d85240006a4387e97fa98b0b4ee61bf6de1e7d39b505c/image-2026-01-07-17-41-44-973.png?cb=abd4a40b1c07c3d3b11d2d6f368836ac) --- version: "v4.1.0" language: "en" --- # Date Operations When a field path resolves to a date string (e.g. created, duedate, updated), you can chain date operations. ## Formatting (returns a string, ends the chain) |--------------------|-----------------------------------------------------------------------|-------------------------------------------| | **Operation** | **Description** | **Example Output** | | .jiraDate | Jira date format | "2024-01-15" | | .jqlDate | JQL date format | "2024-01-15" | | .jiraDateTime | Full Jira datetime | "2024-01-15T09:30:00.000+0000" | | .shortDate | Short date | "1/15/24" | | .shortTime | Short time | "9:30 AM" | | .shortDateTime | Short date + time | "1/15/24 9:30 AM" | | .mediumDate | Medium date | "Jan 15, 2024" | | .mediumTime | Medium time | "9:30:00 AM" | | .mediumDateTime | Medium date + time | "Jan 15, 2024 9:30:00 AM" | | .longDate | Long date | "January 15, 2024" | | .fullDate | Full date with weekday | "Monday, January 15, 2024" | | .fullDateTime | Full date + time with weekday | "Monday, January 15, 2024 9:30:00 AM UTC" | | .format("pattern") | Custom date-fns pattern | "15/01/2024" (using "dd/MM/yyyy") | | .prettyDuration | Render a human-readable string using your Jira time-tracking settings | "3h 20m" | ### Arithmetic --- chainable, returns a date |------------------|--------------------| | **Operation** | **Description** | | .plusDays(n) | Add n days | | .minusDays(n) | Subtract n days | | .plusWeeks(n) | Add n weeks | | .minusWeeks(n) | Subtract n weeks | | .plusMonths(n) | Add n months | | .minusMonths(n) | Subtract n months | | .plusYears(n) | Add n years | | .minusYears(n) | Subtract n years | | .plusHours(n) | Add n hours | | .minusHours(n) | Subtract n hours | | .plusMinutes(n) | Add n minutes | | .minusMinutes(n) | Subtract n minutes | ### Boundaries --- chainable, returns a date |---------------|-------------------------------------------| | **Operation** | **Description** | | .startOfMonth | First moment of the current month | | .endOfMonth | Last moment of the current month | | .startOfWeek | First moment of the current week (Monday) | | .endOfWeek | Last moment of the current week (Sunday) | | .toStartOfDay | Midnight of the same day | ### Setters --- chainable, returns a date |--------------------|------------------------------| | **Operation** | **Description** | | .withDayOfMonth(n) | Set day of month to n | | .withMonth(n) | Set month to n (1 = January) | | .withYear(n) | Set year to n | ### Attributes --- returns a number or string |----------------|-------------|--------------------------------| | **Operation** | **Returns** | **Description** | | .dayOfMonth | number | Day of month (1--31) | | .dayOfWeek | number | ISO day of week (1=Mon, 7=Sun) | | .dayOfWeekName | string | Day name (e.g. "Monday") | | .month | number | Month (1--12) | | .year | number | 4-digit year | | .hour | number | Hour (0--23) | | .minute | number | Minute (0--59) | | .second | number | Second (0--59) | | .weekOfYear | number | ISO week number | ### Comparison --- returns boolean |------------------|------------------------------------------| | **Operation** | **Description** | | .isAfter(date) | true if this date is after the argument | | .isBefore(date) | true if this date is before the argument | | .isEquals(date) | true if both dates are equal | | .compareTo(date) | -1, 0, or 1 | The argument can be an ISO date string or a context path like now or issue.fields.created. ### Diff --- returns an object with numeric properties .diff(date) returns an object with all difference units. The argument can be an ISO date string or a context path (e.g. **now**). |-----------------------------|----------------------------------------| | **Property** | **Description** | | .diff(date).millis | Difference in milliseconds | | .diff(date).seconds | Difference in seconds | | .diff(date).minutes | Difference in minutes | | .diff(date).hours | Difference in hours | | .diff(date).days | Difference in days | | .diff(date).weeks | Difference in weeks | | .diff(date).months | Difference in months | | .diff(date).years | Difference in years | | .diff(date).businessDays | Difference in business days | | .diff(date).prettyPrint | Human-readable (e.g. "3 days 2 hours") | | .diff(date).abs.days | Absolute (unsigned) day difference | | .diff(date).abs.prettyPrint | Absolute human-readable difference | **Date difference examples with now variable** |------------------------------------------------------------|--------------------------------------------------------|--------------------| | **Expression** | **Description** | **Example Output** | | smartValue(issue.fields.created.diff(now).abs.days) | Number of days since creation | 45 | | smartValue(issue.fields.created.diff(now).abs.prettyPrint) | Number of days since creation in human-readable format | 45 days 3 hours | ## Chaining Operations Operations can be chained together. Arithmetic and boundary operations return a date, so you can continue chaining further date operations. |--------------------------------------------------------------------------|-----------------------------------------------| | **Expression** | **Description** | | smartValue(issue.fields.created.plusDays(7).jiraDate) | Created date + 7 days, formatted as Jira date | | smartValue(issue.fields.duedate.startOfMonth.jqlDate) | First day of the due date's month | | smartValue(issue.fields.created.plusMonths(1).withDayOfMonth(1).jqlDate) | First of next month after creation | | smartValue(now.minusDays(30).jiraDate) | 30 days ago from today | | smartValue(issue.fields.components.name.join(" OR ")) | Component names joined with " OR " | --- version: "v4.1.0" language: "en" --- # Example Smart Issue Panel ## What is an "Example Smart Issue Panel"? The Issue Panel is an additional panel in the issue view screen. The panel contains a list of issues based on a dynamic search. Example Smart Issue Panels are the list of issue panels that the app generate when you install the app: * **Smart Issue Links:**Customizable Issue Links panel * **Smart Issues In Epic:**Customizable Issues In Epic panel * **Smart Sub-tasks:**Customizable Sub-tasks panel * **Currently Working On**: List all issues in the current project, assigned to the current user and are not resolved * **All Unresolved Issues**: List all unresolved issues in the current project ### On this page ## Smart Issue Links Get all issues linked with the current issue. JQL query: issue in linkedIssues(value("Key_[issuekey]")) ORDER BY Rank ![image-20221012-085552.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_c8098f85280bf04cda455ca7018436a3c5cf1f72f0c98f9f85f5fa18d54edd32/image-20221012-085552.png?cb=b8e8e8f9a6e23326adfd48c59f3e0ad4) ## Smart Sub-tasks Get all sub-tasks of the current issue. JQL query: parent = value("Key_[issuekey]") ORDER BY Rank ![image-20221012-090027.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_cd8cc0c27413c843df04ba0214fbb8f10918d5c2892149bfb6c2dfa16a1b92b8/image-20221012-090027.png?cb=63e499630d80a4eda7dac66a0ee308f6) ## Smart Issues In Epic Get all issues in the current Epic (if viewing an Epic). JQL query: "Epic Link" = value("Key_[issuekey]") ORDER BY Rank ## Currently Working On List all unresolved issues of the current project that are assigned to the current user. JQL query: assignee = currentUser() AND project = value("Project_[project]") AND resolution = Unresolved ## All Unresolved Issues List all unresolved issues in the current project. JQL query: project = value("Project_[project]") AND resolution = Unresolved --- version: "v4.1.0" language: "en" --- # Export A Smart Issue Panel can be exported as CSV documentation, or printed out. How to export: 1. Click the icon Export 2. Select the type you want to export: CSV/ Print ![image-20221012-101400.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_46d0f3215ce46015da19d139d13933c456cc3ede37969808b02f62b217af5345/image-20221012-101400.png?cb=2874202a496c2763da2fd07b8309dccb) **Note:** The export applies only to the issues on the current page, not all pages in the panel. --- version: "v4.1.0" language: "en" --- # FAQ \& Support * [What is the usage of "Additional JQL Function" in the JQL filter?](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/what-is-the-usage-of-additional-jql-function-in-th.md) * [How can I arrange the order of columns in the panel?](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/how-can-i-arrange-the-order-of-columns-in-the-pane.md) The column order can be changed by drag and drop in the panel configuration page. For this you must be a Jira Administrator. Go the the "Edit Issue Panel" page Click and hold the column you wish to move and drag it to the target location * [What is the usage of "Reset previous"/ "Restore default"?](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/what-is-the-usage-of-reset-previous-restore-defaul.md) Reset previous: The "Reset previous" button is shown whenever you edit panel. It helps to revert all the changes you did in the current editing session to the original state (which were saved in the last time). Restore default: If you click on the "Restore default" button, the column list will restore to the set of default columns (defined by the app): Key, Summary, Status, Assignee. * [How to use search in Issue Panels page?](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/how-to-use-search-in-issue-panels-page.md) When the user types in the input search the issue panels match with search criteria will be shown in the table. By default search by panel name. Single select "Search by" show the type of search: Name \& Scope Name: Search by the name of panel Scope: Search by the scope. User can search by project name, project key Or key "Global" * [What is the difference between Smart Panels DC and Cloud?](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/what-is-the-difference-between-smart-panels-dc-and.md) * [Date Format Consistent with User Settings](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/date-format-consistent-with-user-settings.md) ## **Got an issue, question, or suggestion regarding the Smart Panels for Jira App?** Leave a **comment** on this page and we will provide you with a solution as soon as possible. Optionally, you can send us an [**e-mail**](https://mgm-atlassian-apps.mgm-tp.com/mgm-technology-partners-an-atlassian-partner/latest.md) or contact us via our [**service desk**](https://mgm-tp.atlassian.net/servicedesk/customer/portals). --- version: "v4.1.0" language: "en" --- # How can I arrange the order of columns in the panel? The column order can be changed by drag and drop in the panel configuration page. For this you must be a Jira Administrator. * Go the the "Edit Issue Panel" page * Click and hold the column you wish to move and drag it to the target location ![ArrangeColumn.gif](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_4b35b31bcffc4a026c6599b6d1eb794dd39e1b95e8f294c202c571c62f084f3d/ArrangeColumn.gif?cb=69d21422eee0c6527244e9f4ba04bef2) --- version: "v4.1.0" language: "en" --- # How to use search in Issue Panels page? ![image-20221014-080944.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_dd156d8acc3d66cb32754653a1f28781861b326a6d82d8f3d63ef3e40d4d3c40/image-20221014-080944.png?cb=74551f27b4b2b824ad4dfc82aef5009b) When the user types in the input search the issue panels match with search criteria will be shown in the table. By default search by panel name. Single select "Search by" show the type of search: Name \& Scope * Name: Search by the name of panel * Scope: Search by the scope. User can search by project name, project key Or key "Global" --- version: "v4.1.0" language: "en" --- # Installation Guide ## Prerequisites * You must have **Jira Cloud administrator** permissions. * If you want to enable the Wiki Panel feature, you need an active **Confluence Cloud** instance on the same Atlassian site. ## Guide ### Part 1: Install the App 1. Go to :cog_icon: **\> Apps** or **Apps** \> **Manage your apps** 2. Click **Find new apps**. 3. Search for **Smart Panels for Jira**. 4. Click App \> Click **Try it free** 5. Then click "Start free trial" 6. The plugin will be installed and available. The app "Smart Panels for Jira"will be displayed under **Apps** #### Part 2: Connect Confluence (Wiki Panel) To enable the **Wiki Panel** feature, you need to connect your Confluence instance: 1. Open the app by navigating to **Apps** \> **Smart Panels for Jira**. 2. Go to **Connected Apps** \> **Connections** tab. 3. Locate **Confluence** in the list and click **Connect**. 4. Authorize the connection when prompted. Once connected, the Wiki Panel feature will be available on your Jira. ### Please Note: Licenses have expiration dates. The app can be updated as long as the evaluation license is valid. The app stops working when the license period ends. That means: * No issue panels will be displayed in the issue overview page. * The configuration UI at admin level will be removed. * Stored data in database tables are preserved. --- version: "v4.1.0" language: "en" --- # List Operations When a field path resolves to an array (e.g. labels, components, fixVersions), you can apply list operations to transform or extract values. |----------------|--------------------------------|------------------------------------------------------------|---------------------| | **Operation** | **Description** | **Example** | **Output** | | .first | First element | smartValue(issue.fields.components.name.first) | "API" | | .last | Last element | smartValue(issue.fields.components.name.last) | "Auth" | | .get(n) | Element at index n (0-based) | smartValue(issue.fields.labels.get(1)) | "urgent" | | .getFromEnd(n) | Element n positions from end | smartValue(issue.fields.labels.getFromEnd(0)) | "urgent" | | .distinct | Remove duplicates | smartValue(issue.fields.labels.distinct) | *(unique values)* | | .size | Number of elements | smartValue(issue.fields.labels.size) | 2 | | .sum | Sum of numeric values | smartValue(issue.fields.worklogs.timeSpentSeconds.sum) | *(numeric sum)* | | .average | Average of numeric values | smartValue(issue.fields.worklogs.timeSpentSeconds.average) | *(average)* | | .max | Maximum value | smartValue(issue.fields.worklogs.timeSpentSeconds.max) | *(max)* | | .min | Minimum value | smartValue(issue.fields.worklogs.timeSpentSeconds.min) | *(min)* | | .join(sep) | Join elements with a separator | smartValue(issue.fields.labels.join(" OR ")) | "backend OR urgent" | --- version: "v4.1.0" language: "en" --- # Migrate Smart Panel from Data Center to Cloud Here is what you need to know about migrating your Jira Server/ Data Center instance with Smart Panel for Jira to Jira Cloud. A**utomatic migration between Server/Data Center and Cloud does not exist yet** due to the differences in the programming model and the API. The process of migration involves **manually**moving the configuration of Smart Issue Panel from Server Data Center instance to the cloud Jira. **Feature Differences** Smart Panel for Jira Cloud **does not have the same feature set** as the Server/Data Center version. | **Main Features** | **Server / Data Center** | **Cloud** | |------------------------------|--------------------------|-------------------| | Smart Issue Panels for Jira | available | available | | Smart Wiki Panels for Jira | available | not yet available | | Smart System Panels for Jira | available | not yet available | | Backup | available | not yet available | | Restore | available | not yet available | | System Setting | available | not yet available | | Project Setting | available | not yet available | --- version: "v4.1.0" language: "en" --- # Migration from Additional Function to Smart Values ## 1. Overview The **Additional Function** feature has been replaced by a new and enhanced feature called [**Smart Values**](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/smart-values-in-smart-panels.md) Smart Values provides a more flexible, scalable, and maintainable syntax while delivering equivalent and extended functionality. To ensure a smooth transition and backward compatibility, existing customer configurations that use **Additional Function** will continue to be supported. A dedicated compatibility mechanism is provided to interpret and migrate legacy configurations to the new **Smart Values** syntax. ## 2. Backward Compatibility * Existing configurations using **Additional Function** continue to work * No changes are required for current customers * Legacy data is preserved ## Additional Function - Constructing the JQL Query LEGACY In the section **Content,** we use JQL to construct the search query. The result of this search query is a list of issues that will be displayed in the Smart Issue Panel. * Define your JQL in the **JQL**field. Advanced JQL features like auto-completion, operators, etc. are available. * The **Shared Filters** allocates all filters which are shared with the current user and selected project. Selecting a filter will paste the respective JQL query to the JQL field. You can further edit the query in the JQL field after it has been pasted. * Anadditional JQL function of type `value()` was added to perform a dynamic search on issue-specific values. Select any allocated field in the **Additional Functions** drop-down and a respective `value()` function will be generated and added to the JQL field automatically. ([++See more parse "Smart JQL" to "JQL"++](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/parse-smart-jql-into-jql.md) ) Examples for using the Additional JQL function value() To construct a search based on any of the issues **system fields**, select the respective system field. * To perform a search based on current reporter issues, select "Reporter". The following query will return all issues that are assigned to the current reporter: assignee = value("Reporter_[reporter]") * Whereas the following query will return all issues which have a component in the current issues component list: component in value("Component/s_[components]") To construct a search based on the current issue itself or a search that excludes the current issue, select the system field "Key". * Get a list of all issues linked with the current issue and use it to create your own customized Issue Links panels such as e.g. "Related Bugs". The following query will return all bugs that are linked to the current issue: issue in linkedIssues(value("Key_[issuekey]")) AND issuetype = Bug * To exclude the current issue from the search result you can add the following to your JQL query: key != value("Key_[issuekey]") To construct a search based on any of the issue's **custom fields**, select the respective custom field. * To perform a search based on the value in the field "Customer", select "Customer". The following query will return all issues where the custom field "Client" has the same value as the current issues custom field "Customer": Client = value("Customer_[customfield_10021]") --- version: "v4.1.0" language: "en" --- # Legacy - Parse "Smart JQL" into "JQL" We have introduced a new feature called **Smart Value** , which is designed to replace the legacy **Additional Function** . While **Additional Function** remains available and fully functional in this version, **Smart Value** is the recommended option going forward for new configurations. ## System Fields Syntax of the additional function: **value("** *\* **_\[** *\* **\]")** ***Example:*** "Smart JQL": **project = ATD and assignee = value("Reporter_\[reporter\]") and timespent = value("Time Spent_\[timespent\]")** **=\>**"JQL" project = ATD and assignee = 5b2cb2644bcba343d849b7be and timespent = "2w, 1d" | | **Field** | **JQL Token** | **JQL value** | | | |----|-------------------------|---------------------------------------------------------------|-------------------------------------------------------|-------------------------------------|---------------------------------------------------------------------------------------------------| | 1 | Affects versions | value("Affects versions_\[versions\]") | List of Affects versions 's name | "(Fixver_1, NewFixVer)" / "(EMPTY)" | Only support comparison method **IN** for plural fields. Ex: affectedVersion in (ATD_v1, test_v2) | | 2 | Assignee | value("Assignee_\[assignee\]") | Account Id of Assignee | "5b2cb2644bcba343d849b7be"/ 'null' | | | 3 | Components | value("Components_\[components\]") | List of component 's name | "(ATD_v1, test_v2)" / "(EMPTY)" | Only support comparison method **IN** for plural fields. Ex: components in (ATD_v1, test_v2) | | 4 | Created | value("Created_\[created\]") | Date with format yyyy-mm-dd | "2021-03-25" / "EMPTY" | | | 5 | Creator | value("Creator_\[creator\]") | Account Id of Creator | "5b2cb2644bcba343d849b7be"/ 'null' | | | 6 | Due date | value("Due date_\[duedate\]") | Date with format yyyy-mm-dd | "2021-10-18" / "EMPTY" | | | 7 | Fix versions | value("Fix versions_\[fixVersions\]") | List of fixversion 's name | "(Fixver_1, NewFixVer)" / "(EMPTY)" | Only support comparison method **IN** for plural fields. Ex: fixVersion in (ATD_v1, test_v2) | | 8 | Issue Type | value("Issue Type_\[issuetype\]") | Name of issue type | "Story" / 'null' | | | 9 | Key | value("Key_\[issuekey\]") | Key of issue | "DP-4" / 'null' | | | 10 | Labels | value("Labels_\[labels\]") | List of label | "(ABC, Add_new)" / "(EMPTY)" | Only support comparison method **IN** for plural fields. Ex: labels in (ABC,Add_new) | | 11 | Last Viewed | value("Last Viewed_\[lastViewed\]") | Date with format yyyy-mm-dd | "2021-03-25" / "EMPTY" | | | 12 | Original estimate | value("Original estimate_\[timeoriginalestimate\]") | Value of timespent format ...w,...d,...m,...s | "2w, 1d" / null | | | 13 | Parents | value("Parents_\[parents\]") | Key of parent | "DP-1" / null | | | 14 | Priority | value("Priority_\[priority\]") | Name of Priority | "Medium"/ null | | | 15 | Project | value("Project_\[project\]") | Key of Project | "DP"/ null | | | 16 | Remaining Estimate | value("Remaining Estimate_\[timeestimate\]") | Value of timespent format ...w,...d,...m,...s | "2w, 1d" / null | | | 17 | Reporter | value("Reporter_\[reporter\]") | Account Id of Reporter | "5b2cb2644bcba343d849b7be"/ 'null' | | | 18 | Resolution | value("Resolution_\[resolution\]") | Resolution 's name | "Done" / null | | | 19 | Resolved | value("Resolved_\[resolutiondate\]") | Date with format yyyy-mm-dd | "2021-10-04" / "EMPTY" | | | 20 | Status | value("Status_\[status\]") | Name of Status | "To Do"/ 'null' | | | 21 | Status Category Changed | value("Status Category Changed_\[statuscategorychangedate\]") | Day of Status Category Changed with format yyyy-mm-dd | "2021-10-04" / "EMPTY" | | | 22 | Status Category | value("Status Category_\[statusCategory\]") | Name of Status Category | "To Do" / null | | | 23 | Summary | value("Summary_\[summary\]") | Value of summary | "How to create sprint" / 'null' | | | 24 | Time Spent | value("Time Spent_\[timespent\]") | Value of timespent format ...w,...d,...m,...s | "2w, 1d" / null | | | 25 | Updated | value("Updated_\[updated\]") | Date with format yyyy-mm-dd | "2021-03-25" / "EMPTY" | | | 26 | Votes | value("Votes_\[votes\]") | Number of votes | 5 / 0 | | | 27 | Watches | value("Watches_\[watches\]") | Number of watcher | 2 / 0 | | | 28 | Work Ratio | value("Work Ratio_\[workratio\]") | Value of work ratio | "20" / null | | ## Custom Fields Syntax of the additional function: **value("** *\* **_\[** *\* **\]")** **Example:** "Smart JQL": **labels in value("Labels (cf)_\[customfield_10041\]") OR assignee = value("Mantis Assigned_\[customfield_10236\]")** **=\>**"JQL" labels in ("Hello","Document") OR assignee = 5b2cb2644bcba343d849b7be | | **Field Type** | **Description** | **Value** | **Note** | |----|------------------------------------|------------------------------------|--------------------------------------------------------|---------------------------------------------------------------------------------| | 1 | Select List (cascading) | The list value of cascading select | "(Cat, Black)" / "(EMPTY)" | Only support comparison method **IN** for plural fields. Ex: cf in (Cat, Black) | | 2 | Date Picker | Date with format yyyy-mm-dd | "2021-03-25" / "EMPTY" | | | 3 | Date Time Picker | Date with format yyyy-mm-dd | "2021-03-25" / "EMPTY" | | | 4 | Number Field | Value of field | "50" / 0 | | | 5 | Labels | The list of labels | "(Label1, Label2)" / "(EMPTY)" | Only support comparison method **IN** for plural fields. | | 6 | Select List (single choice) | Value of field | "Select1" / "null" | | | 7 | Select List (multiple choices) | The list value of select | "(A,B") / "(EMPTY)" | Only support comparison method **IN** for plural fields. | | 8 | Group Picker (single group) | Name of a group | "jira-admin" / "null" | | | 9 | Group Picker (multiple groups) | The list value of group | "(A,B") / "(EMPTY)" | Only support comparison method **IN** for plural fields. | | 10 | Project Picker (single project) | The project key | "DP" / "null" | | | 11 | Radio buttons | Value of field | "Radio check" / "null" | | | 12 | Checkboxes | The list value of checkboxes | "(A,B") / "(EMPTY)" | Only support comparison method **IN** for plural fields. | | 13 | Text Field (read only) | Value of field | "Readonly" / "null" | | | 14 | Short text (plain text only) | Value of field | "Text field" / "null" | | | 15 | URL Field | Value of field | "url field" / "null" | | | 16 | User Picker (single user) | Account Id of user | "5b2cb2644bcba343d849b7be"/ 'null' | | | 17 | User Picker (multiple users) | List account Id of users | "(5b2cb2644bcba343d849b7be, 232354dd3r53)" / "(EMPTY)" | Only support comparison method **IN** for plural fields. | | 18 | Version Picker (multiple versions) | The list name of version | "(version1, version2") / "(EMPTY)" | Only support comparison method **IN** for plural fields. | | 19 | Version Picker (single version) | Name of a version | "version1" / "null | | --- version: "v4.1.0" language: "en" --- # Project Administrator Guide Project Administrators can create Issue or Wiki Panels for their projects. They can also view/copy panels that Jira Administrators have configured for their project. ## On this page For all the following procedures, * Smart Panels for Jira app must be installed on your Jira Cloud with a license or trial license (see our [Installation Guide](https://mgm-tp.atlassian.net/wiki/spaces/SP/pages/944768287/Installation+Guide) for detailed instructions). * You must be logged in as a user with the **Administer projects** [project permission](https://confluence.atlassian.com/adminjiraserver/managing-project-permissions-938847145.html). * Smart Panels functionality for at least one System Panel (Issue Links, Sub-Tasks or Issues In Epic)must have been enabled globally by a Jira Administrator. See our [Administrator Guide](https://mgm-tp.atlassian.net/wiki/spaces/SP/pages/944768300/Administrator+Guide) for detailed instructions. ## Create a Smart Issue or Wiki Panel for your project 1. Navigate to your project. 2. Choose "**Space Settings**" 3. From section **Apps** , select **Smart Panels Configuration** 4. On the **Smart Panels for the Project**page, select the tab 1. **Issue Panels:** Clicking "Create Issue Panel" to create an Issue Panels. Learn more: [Smart Issue Panels for Jira](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/smart-issue-panels-for-jira.md) 2. **Wiki Panels:** Clicking "Create Issue Panel" to create a Wiki Panels. Learn more: [Smart Wiki Panels for Jira](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/smart-wiki-panels-for-jira.md) **Note:** Scope can only be modified in the [global administration](https://tiendang.atlassian.net/jira/settings/apps/ee018864-6e2f-4a9f-8566-e271b997db47/46f219e2-2961-4989-9d7e-8efe475b1a0f/issue-panel/mgm_all_unresolved_issue_panels/edit). ## Editing/ View a Smart System, Issue or Wiki Panel in your project 1. Navigate to your project. 2. Choose "**Space Settings**" 3. From section **Apps** , select **Smart Panels Configuration** 4. On the **Smart Panels for the Project**page, select the tab 1. **Issue Panels:** Clicking the panel to edit/view an Issue Panels. Learn more: [Smart Issue Panels for Jira](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/smart-issue-panels-for-jira.md) 2. **Wiki Panels:** Clicking the panel to edit/view a Wiki Panels. Learn more: [Smart Wiki Panels for Jira](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/smart-wiki-panels-for-jira.md) Project administrator can create/edit panels and associate them with all projects for which the user has **project admin permissions**. Only users with the **Jira Administrators** [global permission](https://confluence.atlassian.com/adminjiraserver/managing-global-permissions-938847142.html) are permitted to: * Create a panel with scope Global See our [Administrator Guide](https://mgm-tp.atlassian.net/wiki/spaces/SP/pages/944768300/Administrator+Guide) for detailed instructions. --- version: "v4.1.0" language: "en" --- # Release Notes A short explanation on version numbers Given a version number MAJOR.MINOR.PATCH, increment the: 1. MAJOR version when incompatible API changes are made 2. MINOR version when functionality in a backward-compatible manner is added 3. PATCH version when backward-compatible bug is fixed ## **4.1.0 (02/04/2026)** ### **New Features:** * Added Import/Export functionality to the Features panel. * Introduced Smart Panel with inline editing (Summary, Status, Assignee, Components). * Added collapse/expand for the Features panel. * Enhanced Smart Values with dynamic retrieval and Array function support. **Bug Fixes:** * Fixed images not loading in the popover. *** ** * ** *** ## **4.0.0 (9/02/2026)** ### New Features * **New Wiki Panel** Introduced a new panel type that displays relevant articles from linked Confluence spaces. * **Smart Value** Added a new feature that allows you to write dynamic JQL and CQL queries. * **Improved Issue Panel UI** Updated the Issue Panel in the Issue View with a refreshed and more intuitive interface. * **Powerful Smart Panel for Project Administrators** Introduced an enhanced Smart Panel with project admin--level capabilities. ### **Bug Fixes** * Updated `@forge/api` to `@forge/kvs`. * Fixed date rendering to display the correct format. *** ** * ** *** ## **2.11.0 (07/10/2025)** ### **Bug Fixes** * Update JQL search API *** ** * ** *** ## **2.10.0 (19/09/2025)** ### **Compatibility** * Upgrade to Node20 *** ** * ** *** ## **2.9.0 (10/02/2025)** ### New Features * Improved loading speed with lazy loading for each issue page * Increase maximum issues per page to 100 *** ** * ** *** ## **2.8.0 (05/02/2025)** ### New Features * The number of displayed issues can be configured ### Bug Fixes * The number of displayed issues is limited to 100 issues *** ** * ** *** ## **2.0.0 (10/02/2022)** **The first Cloud version has been released.** ### New Features * Customize the content of Jira built-in panels "Issue Links", and "Sub-tasks",... such as adding additional issue metadata, and adding customized header names by using the example panel created by the app * Customize the layout of the panels on the user interface, such as reordering or ranking columns of the panel. * Limit the number of issues displayed in the panel, and use pagination to browse all issues. * Use the simple and known JQL to define your condition. * Access to already existing filters so implementing JQL from scratch is not needed. * Use the permission concept to limit the visibility of a panel to a group or a project role. * **Additional Functions**, which help you to define even more complex JQL, reflect the dynamic context of the Panel and Issue * Limit "Shared Filter" for "Issue Panel" to those filters which are shared with the corresponding project and currently logged-in user * Export Issue Panel to CSV/Print PDF --- version: "v4.1.0" language: "en" --- # Smart Issue Panel With **Smart Panels for Jira Cloud** app, the user has near-endless possibilities to adapt the issue panels in their projects to their specific needs. With Smart Issue Panel, you can show the relevant information and issues based on any JQL query directly from the Issue View. ## On this page If you need Issue Panel on your issue/project, don't hesitate to get in touch with Jira Administrator. ### **Issue Panel view** ![image-20221012-093610.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_a68eb0c95ecb6169cdf7ae657290c113ef05769c4e708f0e24308755b40d43c8/image-20221012-093610.png?cb=1c43792bfd929445e81e8fe81acd6545) * Columns button: Customize your Issue Panel by show/hide columns. This operation effect only the current session. If you reload the page, all columns config will be restored to the configured state from your Admin. ![image-20221012-093741.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_1fc7c81362942f8db0a113015a648379473790627e776505a34fb1fb73f6c8e2/image-20221012-093741.png?cb=9415fc80ef3535622ba81f8944703791) * Export button: Export the current panel to Excel/ CSV. More information on the [export page](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/export.md) * Sort Issue :sortIcon: : You can click on the column name :columnHeader: to sort the issue by each column. Or you can use the icon :threeDot: to use more features here (pin column, sort, hide) * Drag and drop to rearrange \& resize columns in the panel * The panel has built-in pagination to shorten the long content and make it easier to browse the issues The limitation of issues in the Smart Panels is 100 issues ### **Issue Panel message** * No smart panel is available to show. This could mean that there is no Smart Issue Panel for the current project/issue or you don't have view permission. ![image-20221012-095608.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_8e1c0073d26b4cbe3b4bda918038c0eddd1205ae775a5d691fb1f08b7151ff38/image-20221012-095608.png?cb=17e1c1b386d91aa26234408c1471f931) * JQL error: If any problem occurs in the JQL query. ![image-20221012-095923.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_31f014024cc48c1224130e0d79dc9e8ea333ae71c8ce0cb77fefedb2b362d063/image-20221012-095923.png?cb=12639e5714b499e934753b8c8358672f) If you see another kind of message, it means the configuration of that smart issue panel has a problem. Please make a screenshot or export the message then contact your project admin or Jira administrator. --- version: "v4.1.0" language: "en" --- # Smart Issue Panels for Jira ## What is an "Issue Panel"? The Issue Panel is an additional panel in the issue view screen. The panel contains a list of issues based on a dynamic search. An Issue Panel can be created by Jira Administrators / Project Administrator and can be configured by them ### On this page For all the following procedures, * Smart Panels for Jira app must be installed on your Jira Cloud with a license or trial license (see our [Installation Guide](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/installation-guide.md) for detailed instructions). * You must be logged in as a user with the **Jira Administrators** [global permission](https://confluence.atlassian.com/adminjiraserver/managing-global-permissions-938847142.html). ## Creating a new Issue Panel An Issue Panel is specific to a single project or multi projects or global. If you want to reuse the configuration of an existing Issue Panel, go to step [**Copying an Issue Panel**](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/smart-issue-panels-for-jira.md#SmartIssuePanelsforJira-CopyinganIssuePanel)on this page. 1. Choose :cog_icon: \> **Apps** 2. Navigate to **Smart Panels for Jira Cloud** 3. Click **Create Issue Panel**. 4. Use the form to configure the following attributes and conditions of your panel (See the table below) 5. Click **Save** and you will be redirected to the **Manage Panels**page. | **Section** | **Parameter** | **Description** | **Additional Information** | **Required** | |-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------| | **Details** | **Name** | Enter the name for the panel. Use a self-explanatory panel name so users can understand the purpose of your panel. | Maximum 255 characters | yes | | **Details** | **Description** | Add a description of the panel. | Maximum 4096 characters | no | | **Details** | **Scope** | Select the scope where the panel will be displayed | Global: Apply for all Projects Projects: Apply for specific project/s | yes | | **Details** | **Project** To configure the field Project, the **Scope** "Projects" must be selected | Select the project where the panel will be displayed. | Multi Select Field | yes | | **Details** | **Issue Type** | The Issue Types where the panel will be display, or All Issue Types if this field is empty. | Multi-Select Field Default: "All Issue Types" | no | | **Content** | **JQL** For detailed documentation see [**Constructing the JQL Query**](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/smart-issue-panels-for-jira.md#SmartIssuePanelsforJira-ConstructingtheJQLQuery) | Use JQL ([Jira Query Language](https://www.atlassian.com/blog/jira-software/jql-the-most-flexible-way-to-search-jira-14)) to search for issues. We support the smart value for JQL. | Auto-complete function to suggest writing correct JQL. The validation of the JQL query is performed when displaying the panel to the user. Incorrect JQL semantics will result in an error message in the panel view. | yes | | **Content** | **Max Issues** | The maximum number of issues shown in the panel | Set -1 to indicate an unlimited number of issues | yes | | **Content** | **Shared Filters** | Paste JQL from suggested pre-defined filters to the JQL field. | Suggests all filters which are shared with the current user and selected project. | no | | **Content** | **Results per page** | The maximum number of issues shown in the panel for each page | Min: 1 Max: 100 | yes | | **Content** | **Columns** | Select the metadata of the issue to be displayed. Optionally customize the header. | * To add a new column, select a field from **Add field** input. * By default, field name will be used as the table header if the custom header is empty. * Use **Restore default** to restore the list of 4 pre-defined columns: Key, Summary, Status, Assignee * Use **Reset previous** (only when editing a panel) to undo every changes in the Columns list, and revert to the original columns before editing * Drag and drop a column to set the order of columns in panel view * To delete a column, click on the delete icon | yes | | **Permissions** | **Viewers** | Grant permission to view the panel to certain groups, project roles, etc... * Private: Only viewed by the creator * User: Grant the view permission for specific users * My Organization: Any logged in user on the site * Group: Grant the view permission for specific groups * Project: Select project, project roles for viewing | | yes | ### Supported issue field to show in Smart Issue Panel List of all supported issue fields to show in the Smart Issue Panel. | **System Fields** | **Custom Field Types** | |------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | * Affects versions * Assignee * Attachment * Comment * Components * Created * Creator * Description * Due date * Environment * Fix versions * Images * Issue Type * Key * Labels * Last Viewed * Linked issues * Original estimate * Parents * Priority * Progress * Project * Remaining Estimate * Reporter * Resolution * Resolved * Status * Status Category * Status Category Changed * Sub-tasks * Summary * Time Spent * Updated * Votes * Watches * Work Ratio * Σ Original Estimate * Σ Progress * Σ Remaining Estimate * Σ Time Spent | * Checkboxes * Date Picker * Date Time Picker * Group Picker (multiple groups) * Group Picker (single group) * Labels * Number Field * Paragraph (supports rich text) * Project Picker (single project) * Radio buttons * Select List (cascading) * Select List (multiple choices) * Select List (single choice) * Short text (plain text only) * Text Field (read only) * URL Field * User Picker (multiple users) * User Picker (single user) * Version Picker (multiple versions) * Version Picker (single version) | *** ** * ** *** For the following procedures, at least one Issue Panel must already exist. For all the following Actions: 1. Choose :cog_icon: \> **Apps**. 2. From section **APPS** , select**Smart Panels for Jira Cloud**. **Tip:** * You can search your panels by **Name** or**Scope**. ## Editing an Issue Panel 1. Locate the desired Issue Panel and click :button_action: \> **Edit**. / Or locate the desired Issue Panel → click on the name 2. On the **Edit Panel**page, use the form to configure the attributes and conditions of the panel (see the above table). 3. Click **Save** and you will be redirected back to the **Dashboard** page. ## Copying an Issue Panel 1. Locate the desired Issue Panel and click :button_action: \> **Copy**. 2. The new copy issue panel will be added to the list of issue panels. The copy panel has a name with the syntax: "\[original_name\] - Copy" ## Enabling/Disabling an Issue Panel 1. Locate the desired panel and click the toggle button **Status** ## Removing an Issue Panel 1. Locate the desired Issue Panel and click :button_action: \> **Delete**. 2. Confirm the deletion by clicking **Delete**. --- version: "v4.1.0" language: "en" --- # Smart Values in Smart Panels ## On this page ### What you will learn here On this page, you'll learn what **Smart Values in Smart Panel** are, how they work in JQL/ CQL, and how to use them. *** ** * ** *** ### Overview The **Smart Value in Smart Panel** feature allows you to use **dynamic values** in your JQL (Jira Query Language), CQL (Confluence Query Language) queries instead of hardcoding static values. This makes your queries more **flexible, reusable, and easier to maintain**, since they automatically adapt to the context of the issue. ### How The Smart Value Works Smart Values in Smart Panel reference fields within an issue dynamically. The syntax is: |--------------------------| | smartValue() | * `` represents the JSON path of the issue field. * At runtime, this will be replaced with the actual field value from the issue. The data you can access with these Smart Values comes directly from the **Jira Issue API** : [GET /rest/api/3/issue/{issueIdOrKey}](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-get) This means any field returned by that API can be used in a Smart Value expression. |------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | { "id": "10002", "key": "ED-1", "fields": { "priority": { "name": "High" }, "issuetype": { "name": "Bug" }, "project": { "key": "EX", "name": "Example" }, "status": { "name": "Open" }, "description": { "type": "doc", "content": [ ... ] }, "comment": [ { "id": "10000", "body": { "type": "doc", "content": [ ... ] } } ], "worklog": [ { "timeSpent": "3h 20m" } ] } } | ### **Example** **JQL with Smart Values (Dynamic)** |-----------------------------------------------------------------------------------------------------------| | priority = smartValue(issue.fields.priority.name) AND issuetype = smartValue(issue.fields.issuetype.name) | Here: * `smartValue(issue.fields.priority.name)` → Gets the **priority of the current issue**. * `smartValue(issue.fields.issuetype.name)` → Gets the **issue type of the current issue**. This query automatically adapts to whichever issue it is applied to, without requiring manual edits. For a ticket such as *ATD-1* with priority set to High and issue type set to Bug, the JQL is: |-----------------------------------------| | priority = "High" AND issuetype = "Bug" | **CQL with Smart Values (Dynamic)** |-----------------------------------------------------------------------| | type = page and creator = smartValue(issue.fields.assignee.accountId) | Here: * `smartValue(issue.fields.assignee.accountId)` → Gets the **account Id assignee of the current issue**. This query automatically adapts to whichever issue it is applied to, without requiring manual edits. For a ticket such as *ATD-1* with assigne set to user have Id: "122-884-dd02-ddffs", the CQL is: type = page and creator = "122-884-dd02-ddffs" --- version: "v4.1.0" language: "en" --- # Smart Wiki Panels for Jira ## What is a "Wiki Panel"? The Wiki Panel is an additional panel in the issue view screen. The panel contains a list of links which are knowledge that is stored in Confluence and are specifically provided to assist the current user in the process of completing his/her task. A Wiki Panel can be created by Jira Administrators/ Project Administrators and can be configured by them. ### On this page For all the following procedures, * Smart Panels for Jira app must be installed on your Jira Cloud with a license or trial license (see our [Installation Guide](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/installation-guide.md) for detailed instructions). * You must be logged in as a user with the **Jira Administrators** [global permission](https://confluence.atlassian.com/adminjiraserver/managing-global-permissions-938847142.html). ## Creating a new Wiki Panel An Wiki Panel is specific to a single project or multi projects or global. If you want to reuse the configuration of an existing Wiki Panel, go to step [**Copying an**](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/smart-issue-panels-for-jira.md#CopyinganIssuePanel)**Wiki Panel**on this page. 1. Choose :cog_icon: \> **Apps** 2. Navigate to **Smart Panels for Jira Cloud** 3. Click **Create Wiki Panel**. 4. Use the form to configure the following attributes and conditions of your panel (See the table below) 5. Click **Save** and you will be redirected to the **Manage Panels**page. | **Section** | **Parameter** | **Description** | **Additional Information** | **Required** | |-----------------|---------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------| | **Details** | **Name** | Enter the name for the panel. Use a self-explanatory panel name so users can understand the purpose of your panel. | Maximum 255 characters | yes | | **Details** | **Description** | Add a description of the panel. | Maximum 4096 characters | no | | **Details** | **Scope** | Select the scope where the panel will be displayed | Global: Apply for all Projects Projects: Apply for specific project/s | yes | | **Details** | **Project** To configure the field Project, the **Scope** "Projects" must be selected | Select the project where the panel will be displayed. | Multi-Select Field | yes | | **Details** | **Issue Type** | The Issue Types where the panel will be display, or All Issue Types if this field is empty. | Multi-Select Field Default: "All Issue Types" | no | | **Content** | **Filter By** | Select filter by CQL or BUILDER | Select type for wiki panel search | yes | | **Content** | **CQL** Available when **Filter By** is set to **CQL** | Use CQL ([Confluence Query Language](https://developer.atlassian.com/cloud/confluence/advanced-searching-using-cql/)) to search for issues. | CQL also support the [Smart Value](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/smart-values-in-smart-panels.md) for configuration | | | **Content** | **BUILDER** Available when **Filter By** is set to **CQL** | Use CQL Builder UI to search for issues. More details see below: [Smart Wiki Panels for Jira \| Builder](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/smart-wiki-panels-for-jira.md#Builder) | | | | **Content** | **Max Contents** | The maximum number of page/blog.. shown in the panel | Set -1 to indicate an unlimited number of contents | yes | | **Content** | **Results per pag** | The maximum number of contents shown in the panel for each page | Min: 1 Max: 100 | yes | | **Content** | **Columns** | Select the metadata of the issue to be displayed. Optionally customize the header. | * To add a new column, select a field from **Add field** input. * By default, field name will be used as the table header if the custom header is empty. * Use **Restore default** to restore the list of 4 pre-defined columns: Key, Summary, Status, Assignee * Use **Reset previous** (only when editing a panel) to undo every changes in the Columns list, and revert to the original columns before editing * Drag and drop a column to set the order of columns in panel view * To delete a column, click on the delete icon | yes | | **Permissions** | **Viewers** | Grant permission to view the panel to certain groups, project roles, etc... * Private: Only viewed by the creator * User: Grant the view permission for specific users * My Organization: Any logged in user on the site * Group: Grant the view permission for specific groups * Project: Select project, project roles for viewing | | yes | ### Supported issue field to show in Smart Wiki Panel List of all supported issue fields to show in the Smart Wiki Panel. | **Support Fields** | |--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | * Url * Title * Id * Status * Excerpt * Created * Creator * Label * LastUpdatedDate * LastUpdatedUserName * LastEditTime * SpaceKey * SpaceTitle * SpaceType * SpaceStatus * LikedPage * History | ### Constructing the CQL Query In the section **Content,** we use CQL to construct the search query. The result of this search query is a list of issues that will be displayed in the Smart Wiki Panel. * Define your CQL in the **CQL**fields * **Smart Values** are supported when writing CQL. They enable dynamic searches based on issue-specific values. Learn more: [Smart Values in Smart Panels](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/smart-values-in-smart-panels.md) ### Builder Use the link **Add a filter**to see all available filters. From the drop-down menu, select the relevant filter. The additional filter field can be removed via the cross button. | **Parameter** | **Description** | **CQL parse** | |-----------------|---------------------------------------------|---------------------------------| | Text | Text field to search by text | text \~ "\" | | In Space | Multi-select to search by Space | spaces IN (\) | | With title | Text field to search by title | title\~"\" | | Label | Multi-select to search by Label | label IN (\) | | Type | Multi-select to search by Type | type IN (\) | | Creator | Multi-select users to search by Creator | creator IN (\) | | Contributor | Multi-select users to search by Contributor | contributor IN (\) | | Mentioning user | Multi-select uses to search by Mentioning | mention IN (\) | | Created | Single select to search by created | createded \>= \ ,... | | Last Updated | Single select to search by lasted updated | lastmodified \>= \,.... | Example of a CQL query with all criteria 'text~"text search" AND space="space-1" AND title~"hello" AND label IN ("Bug","Feature") AND type IN ("page","comment") AND creator IN ("fdfd-1ae8-sde-b1e7-200117b81f85","5bd45e3d849b7be") AND contributor IN ("ff8sd50c-1aeff8-44e2-b1e7-117b81f85","52sdsdba343d849b7be") AND mention IN ("6285efef222d360ssdf7","1ae8-44e2-b1e7-200117b81f85") AND created>="2025-12-16" AND created<="2025-12-23" AND lastmodified>="2025-12-16" AND lastmodified<="2025-12-23" ' *** ** * ** *** For the following procedures, at least one Wiki Panel must already exist. For all the following Actions: 1. Choose :cog_icon: \> **Apps**. 2. From section **APPS** , select**Smart Panels for Jira Cloud**. The limitation of issues in the Smart Panels is 100 issues **Tip:** * You can search your panels by **Name** or**Scope**. ## Editing a Wiki Panel 1. Locate the desired Wiki Panel and click :button_action: \> **Edit**. / Or locate the desired Wiki Panel → click on the name 2. On the **Edit Panel**page, use the form to configure the attributes and conditions of the panel (see the above table). 3. Click **Save** and you will be redirected back to the **Dashboard** page. ## Copying a Wiki Panel 1. Locate the desired Wiki Panel and click :button_action: \> **Copy**. 2. The new copy issue panel will be added to the list of issue panels. The copy panel has a name with the syntax: "\[original_name\] - Copy" ## Enabling/Disabling a Wiki Panel 1. Locate the desired panel and click the toggle button **Status** ## Removing a Wiki Panel 1. Locate the desired Wiki Panel and click :button_action: \> **Delete**. 2. Confirm the deletion by clicking **Delete**. --- version: "v4.1.0" language: "en" --- # User Guide ![Administrator-Guide.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_f3bfff56473159f5eed307f121b156cc6d97ec8494870b4ce21a6d5f899664c2/Administrator-Guide.png?cb=7e54230d43b5119c561c7ccb39888248) ## This guide includes information on: * [Smart Issue Panel](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/smart-issue-panel.md) * [Export](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/export.md) --- version: "v4.1.0" language: "en" --- # What is the difference between Smart Panels DC and Cloud? | **Feature** | **DC/Server** | **Cloud** | |----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | [System Panel](https://mgm-tp.atlassian.net/wiki/spaces/SP/pages/944768370/Smart+System+Panels+for+Jira) | ![check mark](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_30d65a124261dc6553c5121ef2eeabb310b38867471eb2cd607c90865b58afea/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![cross mark](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_1d812ff734aa6eb9e28e897be031835fa2f6dc6fc1953a9502d76ade0d8e0161/atlassian-cross_mark?cb=a9c671cfc7809253be52d640dbbf1019) | | [Issue Panel](https://mgm-tp.atlassian.net/wiki/spaces/SP/pages/944768431/Smart+Issue+Panels+for+Jira) | ![check mark](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_30d65a124261dc6553c5121ef2eeabb310b38867471eb2cd607c90865b58afea/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_30d65a124261dc6553c5121ef2eeabb310b38867471eb2cd607c90865b58afea/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Create statistics sum(), mean(), min() and max() on the content of the Issue Panel. | ![check mark](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_30d65a124261dc6553c5121ef2eeabb310b38867471eb2cd607c90865b58afea/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![cross mark](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_1d812ff734aa6eb9e28e897be031835fa2f6dc6fc1953a9502d76ade0d8e0161/atlassian-cross_mark?cb=a9c671cfc7809253be52d640dbbf1019) | | Export the content of the Smart Issue Panel to EXCEL or CSV. | ![check mark](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_30d65a124261dc6553c5121ef2eeabb310b38867471eb2cd607c90865b58afea/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_30d65a124261dc6553c5121ef2eeabb310b38867471eb2cd607c90865b58afea/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) CSV and Print | | [Wiki Panel](https://mgm-tp.atlassian.net/wiki/spaces/SP/pages/944768389/Smart+Wiki+Panels+for+Jira) | ![check mark](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_30d65a124261dc6553c5121ef2eeabb310b38867471eb2cd607c90865b58afea/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_30d65a124261dc6553c5121ef2eeabb310b38867471eb2cd607c90865b58afea/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | * **General features** * use custom header names * customize the order of columns * add pagination to your panel * disable panels if temporarily not needed * configure visibility for specific project roles and user groups * give project administrators the ability to configure their own project's panel * copy a Smart Panel to reuse the configuration | ![check mark](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_30d65a124261dc6553c5121ef2eeabb310b38867471eb2cd607c90865b58afea/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_30d65a124261dc6553c5121ef2eeabb310b38867471eb2cd607c90865b58afea/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Project Admin view/edit panel | ![check mark](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_30d65a124261dc6553c5121ef2eeabb310b38867471eb2cd607c90865b58afea/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_30d65a124261dc6553c5121ef2eeabb310b38867471eb2cd607c90865b58afea/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Project Admin create new panel | ![cross mark](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_1d812ff734aa6eb9e28e897be031835fa2f6dc6fc1953a9502d76ade0d8e0161/atlassian-cross_mark?cb=a9c671cfc7809253be52d640dbbf1019) | ![check mark](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_30d65a124261dc6553c5121ef2eeabb310b38867471eb2cd607c90865b58afea/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Panel associated for multiple projects | ![cross mark](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_1d812ff734aa6eb9e28e897be031835fa2f6dc6fc1953a9502d76ade0d8e0161/atlassian-cross_mark?cb=a9c671cfc7809253be52d640dbbf1019) | ![check mark](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_30d65a124261dc6553c5121ef2eeabb310b38867471eb2cd607c90865b58afea/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | Smart value / Additional Function | ![check mark](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_30d65a124261dc6553c5121ef2eeabb310b38867471eb2cd607c90865b58afea/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![check mark](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_30d65a124261dc6553c5121ef2eeabb310b38867471eb2cd607c90865b58afea/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | [Backup](https://mgm-tp.atlassian.net/wiki/spaces/SP/pages/944768466/Backup) | ![check mark](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_30d65a124261dc6553c5121ef2eeabb310b38867471eb2cd607c90865b58afea/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | | | [Restore](https://mgm-tp.atlassian.net/wiki/spaces/SP/pages/944768497/Restore) | ![check mark](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_30d65a124261dc6553c5121ef2eeabb310b38867471eb2cd607c90865b58afea/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) | ![cross mark](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_1d812ff734aa6eb9e28e897be031835fa2f6dc6fc1953a9502d76ade0d8e0161/atlassian-cross_mark?cb=a9c671cfc7809253be52d640dbbf1019) | | Migration Tool | ![cross mark](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_1d812ff734aa6eb9e28e897be031835fa2f6dc6fc1953a9502d76ade0d8e0161/atlassian-cross_mark?cb=a9c671cfc7809253be52d640dbbf1019) | | --- version: "v4.1.0" language: "en" --- # What is the usage of "Additional JQL Function" in the JQL filter? Use this feature to perform an issue-dependent search. The field "Additional JQL Function" will suggest a list of all custom fields from type numeric, text, single select,... and Jira system fields. Selecting an option from this field will build up the JQL function `value()` with a specified field and paste it into the JQL box. The function performs a calculation on the specific field and returns a value from the issue in which the Issue Panel is displaying. The full document on [Smart Issue Panels for Jira](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/smart-issue-panels-for-jira.md) For example: * `"Epic Link" = value("Epic Link_[epiclink]") `→ returns all issues that have an epic link with the current issue. * `assignee= value("Reporter_[reporter]") `→ returns all issues that have been reported by the reporter of the current issue. * `Client = value("Customer_[customfield_10032]")`→ returns all issues that have the same value in the Client field as the current issue in the Customer field. Note that JQL searches do not return empty fields in the results. Parse Additional JQL Function to JQL document on [Parse "Smart JQL" into "JQL"](https://mgm-atlassian-apps.mgm-tp.com/smart-panel-for-jira-cloud/latest/parse-smart-jql-into-jql.md) --- version: "v4.1.0" language: "en" --- # What is the usage of "Reset previous"/ "Restore default"? * **Reset previous:** The "**Reset previous**" button is shown whenever you edit panel. It helps to revert all the changes you did in the current editing session to the original state (which were saved in the last time). * **Restore default:** If you click on the "**Restore default** " button, the column list will restore to the set of default columns (defined by the app): Key, Summary, Status, Assignee. ![image-20221102-031941.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_a5e52f9e89bac4bc863b51ea83d0135b2502f2d63bc4fe2c4e1ddc006765425b/image-20221102-031941.png?cb=6ee40137cc964b19a6f7bad897ecab81) --- version: "v2.0.0" language: "en" --- # Link Workflow Graphic for Jira ## Documentation * ### [Introduction](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/latest/introduction.md) * ### [Download \& Installation](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/latest/download-installation.md) ### [Administrator Guide](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/latest/administrator-guide.md) * ### [User Guide](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/latest/user-guide.md) ### [License](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/latest/license.md) ### [Troubleshooting Articles](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/latest/troubleshooting-articles.md) * ### [Support](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/latest/support.md) * ### [FAQ](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/latest/faq.md) * ### [Release Notes](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/latest/release-notes.md) --- version: "v2.0.0" language: "en" --- # Administrator Guide ## Preconditions *** ** * ** *** * **Link Workflow Graphic for Jira**Add-on is already installed on your JIRA server with a license or trial license * You must be logged in as a user with the **JIRA Administrators** [global permission](https://confluence.atlassian.com/adminjiraserver/managing-global-permissions-938847142.html) ## Step by step guide *** ** * ** *** Here are the exact steps you should take to setup a Workflow Graphic. Click on the links to get to the detailed introduction. 1. [Create a Graphic Language Scheme](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/latest/configure-graphic-language-schemes.md) 1. Add a graphic 2. Associate it with a language 2. Create a [Workflow Graphic Scheme](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/latest/configure-workflow-graphic-scheme.md) 1. Associate a workflow with the *Graphic Language Scheme* set in previous step 3. [Associate your project](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/latest/configure-project.md) with the Language Scheme set in previous step ## Backup and Restore configurations *** ** * ** *** ## Backup **Link Workflow Graphic for Jira** provides the ability to back up all your configuration for "Link Workflow Graphic for JIRA" add-on. Go to [Create Backup](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/latest/create-backup.md) for more information. ## Restore To find out how to restore Workflow Graphic configuration from a backup follow this [link](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/latest/restore-from-backup.md). --- version: "v2.0.0" language: "en" --- # Configure Graphic Language Schemes ## Step by step guide *** ** * ** *** 1. Click the cog icon ![https://confluence.atlassian.com/adminjiraserver/files/951394526/951394527/1/1527598493234/cog_icon.png](https://confluence.atlassian.com/adminjiraserver/files/951394526/951394527/1/1527598493234/cog_icon.png) and choose **Add-ons** from the drop-down menu ![image2018-12-19_14-40-54.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_12119d1dcc742b1ced207b0a8c15cb0d4b6b4c81f9274bffd0ce86f2fe48e89d/image2018-12-19_14-40-54.png?cb=100cd1a5932288b5de86c9223773021f) 2. Go to the **Add-ons Administration** page. On the left side of this page, under**WORKFLOW GRAPHICS** section, select **Graphic Language Schemes** ![image2018-12-20_14-45-33.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_f836525928043f49a3161a6c70100ff028a968eb05582f68dbf547f7b2bc0d91/image2018-12-20_14-45-33.png?cb=ecdd268c24efc674c0f02df38213e82c) 3. In **View Graphic Language Schemes** page, click ![image2018-12-20_14-56-2.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_70f3819759573a6a85d163402293e12d4f2d81b618a063ed162e7dde83bc18d5/image2018-12-20_14-56-2.png?cb=f57d3764a1d9669552bfc084c1b4f188) . 4. In the popup window, enter the name and description for your scheme, and then click **Add** . Note that the name field is required, the description is optional. ![image2018-12-20_15-9-51.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_ffbd061b6c11a196b1aac668f7dea48655b225731713ef63b6f9b8cef42eccd0/image2018-12-20_15-9-51.png?cb=10953bd23b32355a9e82da9aaa84ba11) Once the creation successfully, you will be redirected to **Configuration Graphic Language Scheme** page, with your scheme name on the title. ![image2018-12-20_15-15-5.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_d75768835597aba64634caa2aa2b68428ac42d11865fade360c0503608157511/image2018-12-20_15-15-5.png?cb=8f3d57f11feb7a278639aa1920974a3c) 5. Click on the ![image2018-12-20_16-30-48.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_9fc200f12af878d077e4f65f27ffcd42a51bb0b7b65d12b43e1947ac526d823c/image2018-12-20_16-30-48.png?cb=0ae4004779a7252d166ec79c5484beb0) to go to **Add Graphic Language Entry** page, here you can associate your graphic with a language. ![image2018-12-20_16-35-36.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_3a85981a6da7b28f984b40a72dcafdaad6276ffcf961932ce873eeadc748dae4/image2018-12-20_16-35-36.png?cb=5cc23c91418cb9ebd8818a0d3eeb6352) Here you have 3 options to add a graphic: + Use an URL + Upload an image from your computer + Choose one from all existed graphics After choosing a language and specifying the graphic, click **Add** . If successful, you will be directed back to the **Configuration Graphic Language Scheme** page, where you should see your new entry in the list ![image2018-12-20_16-43-36.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_cedaa0a10f4e8700cb17bda4c6888e8689b0370b40d748ade8d93e8bd5da1c46/image2018-12-20_16-43-36.png?cb=390878eb9b8f614ff173f3b152e61dba) 6. Go back to **View Graphic Language Schemes** page by clicking again on **Graphic Language Schemes** on the left navigation. Your scheme should be seen in the list. ![image2018-12-20_16-50-43.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_a153f82b29aa7e9e2a03b3d086cc20c3cff94e1acf016de5a9b8898c200a96a2/image2018-12-20_16-50-43.png?cb=ff7a25e09912cf7ade717ddc1530e338) You are done with **Graphic Language Scheme** configuration. --- version: "v2.0.0" language: "en" --- # Configure Project ## Step by step guide *** ** * ** *** 1. Go to **Add-ons** page as step 1 at [Configure Graphic Language Schemes](https://mgm-tp.atlassian.net/wiki/pages/resumedraft.action?draftId=86638607#AdministratorGuide-ConfigureGraphicLanguageSchemes) 2. In **Add-ons** page, click on the link **Project Configurations** under **Workflow Graphic** section. You will go to **View Project Workflow Graphic Configurations** page, where you will see a list of projects you have. ![image2018-12-20_17-41-40.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_02e1cb8396439c5faf4ea257726a092c3c0b516bbdc87eb8061c31d907f9178f/image2018-12-20_17-41-40.png?cb=e060ea60ea81dd029c8fdf1dc109acad) 3. Click **Edit** on the project that you want to configure. Next, go to the **Edit Project Association** page and decide if you want to use a standard workflow of Jira for your project or use your custom workflow by check or uncheck the checkbox **Standard Workflow.** If the checkbox **Standard Workflow** is unchecked you will see a list of all already existing **Workflow Graphic Scheme** by expanding the content of the field "**Workflow Graphic Scheme** ". Choose your target **Workflow Graphic Scheme** to assign it to your project. Then click **Update** ![image2018-12-20_17-51-18.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_312875d19f12dc23e31793ce0c317b69a33238a67d2a6953e76e2719bc3f6c11/image2018-12-20_17-51-18.png?cb=3d3d6cdaa4417354c0e60c3826c34c23) Now you should be sent back to the **View Project Workflow Graphic Configurations**page and you should see your project is in the configuration you made. ![image2018-12-20_17-54-14.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_f54580aa4799fb67022d15fa5fa4abcd9215e4326451ed318b5038159306c121/image2018-12-20_17-54-14.png?cb=a75ab35148f03234a7b59f1374cea073) You are now done with the **Configure a Workflow Graphic** for the project. Next, you will be shown how to backup and restore your configuration. --- version: "v2.0.0" language: "en" --- # Configure Workflow Graphic Scheme ## Step by step guide *** ** * ** *** 1. Go to **Add-ons Administration** page and click on [Configure Graphic Language Schemes](https://mgm-tp.atlassian.net/wiki/pages/viewpage.action?pageId=86606134) 2. On the left navigation, under**WORKFLOW GRAPHICS** section, select **Workflow Graphic Schemes** to go to the **View Workflow Graphic Schemes** page ![image2018-12-20_17-10-9.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_c5f99a2ac44e7cfaede33aa5d7889acce499e83a35d044fd34c8db9e3e890c81/image2018-12-20_17-10-9.png?cb=41ccaa6c74c51fdb634ddc1fefab8b3c) 3. Click on the button ![image2018-12-20_17-11-23.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_30ac167f4cd6fa9ce31319dd520d28efd946357ed397bd747f0d83f8e47db951/image2018-12-20_17-11-23.png?cb=bb902c5db11152b2cbcd64140f2f2d74) 4. On the **Add Workflow Graphic Scheme** popup window, enter name (required) and description of your scheme. Then click **Add.** ![image2018-12-20_17-15-13.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_abf392d2c90737a88d56c9faf66d6a016e3b39d8ea73a87ad3fee75bb5ae6bee/image2018-12-20_17-15-13.png?cb=cd15030131fe642af867c47da68c59a9) Once the creation successfully, you will be redirected to **Configuration Workflow Graphic Scheme** page, with your scheme name on the title ![image2018-12-20_17-18-1.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_b12706abae6c2f4ea57ec88388e5a8fea9942195cbb5d80bc337f5e230c40568/image2018-12-20_17-18-1.png?cb=da552a57f0a28f9f7659730d40d6a9ac) 5. Click on the ![image2018-12-20_17-18-46.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_8b2c3e4c7dec5282c8244fe9b479b7310e7a43a1553d2d6b197e3e8d1cb36fd8/image2018-12-20_17-18-46.png?cb=8cc7700fa9ae87391b1a373294cbe917) to map your Graphic Language Scheme with any standard Jira Workflow. In the popup window, choose the Jira workflow that you want to be replaced by your**Graphic Language Scheme** then click **Add** . ![image2018-12-20_17-25-36.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_a17520ef5b8943f111c9a330092ccc8bab7637ace0c0151b568d37b33da584c5/image2018-12-20_17-25-36.png?cb=beeb1d8c7a01a9c4a8df1b5f802ca4a1) If it is successful, the popup will disappear, and you will see a new config added to the list. ![image2018-12-20_17-29-53.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_c845fa989fe1c771f287a8436683bf5818b3734bd0ef7f26def301a5edac4eae/image2018-12-20_17-29-53.png?cb=eafecf24e4ebb7655a672e0de16da9d1) 6. To go back to **View Workflow Graphic Schemes** page, click again on **Workflow Graphic Schemes** on the left navigation. Your scheme should be placed in the list now. ![image2018-12-20_17-32-11.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_19cc777bba2f4e2a6ecfb81d3fe425ef0d196e3fec44379b0a59ec9c5b122158/image2018-12-20_17-32-11.png?cb=332258780fd0d41f3900f39660a96d18) You are done with the configuration of **workflow graphic scheme** and can use it in your project. The next step is to associate this **workflow graphic scheme** with your project. --- version: "v2.0.0" language: "en" --- # Create Backup This page describes how to back up your **Workflow Graphic** data. You need to create a back up if you plan to upgrade your server to a new Jira revision or split your Jira instance. To create a backup follow the steps below. * Choose ![https://confluence.atlassian.com/adminjiraserver/files/951394526/951394527/1/1527598493234/cog_icon.png](https://confluence.atlassian.com/adminjiraserver/files/951394526/951394527/1/1527598493234/cog_icon.png) **\>** **Add-ons**. * Select **WORKFLOW GRAPHICS \> Backup CONFIGURATION**to open the Backup Workflow graphic data page. ![https://wiki.mgm-tp.com/confluence/download/attachments/128853296/WFG_backup_1840x900px.png?api=v2](https://wiki.mgm-tp.com/confluence/download/attachments/128853296/WFG_backup_1840x900px.png?api=v2) The location of workflow graphics XML backup is displayed on this page. The location of workflow graphics XML backup is displayed on this page. * Type the name of the backup file in the **"File name"** field Ensure that Jira has the necessary file system permissions to write to this location. * Click the **'Backup'** button and wait while your Jira data is backed up. * When the backup is complete, a message will be displayed, confirming that Jira has written its data to the file you specified. --- version: "v2.0.0" language: "en" --- # Download \& Installation ## Preconditions *** ** * ** *** * You must be logged in as a user with the **JIRA Administrators** [global permission](https://confluence.atlassian.com/adminjiraserver/managing-global-permissions-938847142.html) ## Download and install *** ** * ** *** ### Download the add-on directly from Atlassian Marketplace 1. Click the cog icon ![image2018-12-19_14-52-42.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_59822009951ac40f7dcbc81a2e1bf19ed122082dd3258f70076b1f0aa100be38/image2018-12-19_14-52-42.png?cb=e75492c19448d6d85bb7792ae72bacb8) and choose **Add-ons** from the drop-down menu ![image2018-12-19_14-40-54.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_e9248f4d55330fb14214b895b2a707bf52196901516fc43cf0b54f6d7ee0cc7a/image2018-12-19_14-40-54.png?cb=100cd1a5932288b5de86c9223773021f) 2. You will be redirected to **Atlassian Marketplace for JIRA** page. In the **Search the Marketplace** box, enter "**Link Workflow Graphic for JIRA** " then press Enter ![image2018-12-19_15-0-52.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_1cb609c8c06b990acfde342aec9ea20478cbe51fa456d9a16255121e4e75f560/image2018-12-19_15-0-52.png?cb=2b783f85c704db630aa0c66c2ca051f0) 3. In the search result list, you should see a plugin called **Link Workflow Graphic for Jira.** Click **Buy now** (or **Free trial** if you want a 30-day trial version). ![image2018-12-19_15-12-49.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_fbae40276fb083a7f98bae3c95a252a35b006a2c961172f248924c2bcf9ca972/image2018-12-19_15-12-49.png?cb=394b7701d1ac6263bdadc541d314521e) 4. Once the purchase process is completed, the plugin will install automatically ![image2018-12-19_15-18-42.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_5013549649b12673d16f47cd822ed16d84ebdc1767ffa32404f1d63fb0fc05c8/image2018-12-19_15-18-42.png?cb=8f5264983d926932b4e9520ce8af4983) 5. Add-on **Link Workflow Graphic for JIRA**will be displayed under **User-installed add-ons** ![https://mgm-tp.atlassian.net/wiki/download/attachments/86540302/WFG_Download&Install_step_6.png?version=1&modificationDate=1544785196959&cacheVersion=1&api=v2&height=400](https://mgm-tp.atlassian.net/wiki/download/attachments/86540302/WFG_Download&Install_step_6.png?version=1&modificationDate=1544785196959&cacheVersion=1&api=v2&height=400) 6. For further licensing and purchasing information check the link [**License**](https://mgm-tp.atlassian.net/wiki/spaces/HCF/pages/73728004/License)in the left navigation --- version: "v2.0.0" language: "en" --- # Enabling logging for "Link Workflow Graphic for JIRA" plugin ## Problem Logging can be useful in diagnosing problems when the cause is not clear. If a Problem occurs in our add-on, you can send us your JIRA Log file. Logging can be useful in diagnosing problems and helps us to solve the problem faster. This How-To describes the steps to create the required log files. ## Precondition You must be logged in as a user with the **JIRA Administrators** [global permission](https://confluence.atlassian.com/adminjiraserver/managing-global-permissions-938847142.html) ## Solution ### **Step 1:** Go to JIRA **Administration** \>**System** \>**Logging and profiling** ![EnabeLogging_step_1.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_7451d2e27b31e6a067e97390183780acc08b416b085873b476fe6debfaa2ba36/EnabeLogging_step_1.png?cb=ccbfd241f6e40f0961e4a6f9e40e61b3) #### **Step 2:** Under Default Loggers, click "**configure logging level for another package** " #### **Step 3:** For Package name enter com.mgmtp.jira.plugin.workflowgraphic #### **Step 4:** For Logging Level select **DEBUG** #### **Step 5:** Press **Add** to save ![WFG_enableLog_step_2_3_4_5.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_08e45ab126ae672fd2b8299d8d424c6f82c8053c1a3ca8c0ffe40cd5b49540e1/WFG_enableLog_step_2_3_4_5.png?cb=a36cbff3cf36741f975795bdd3adadb7) #### **Step 6:** "Link Workflow Graphic for JIRA" plugin log output will now be added to JIRA's own `atlassian-jira.log` file #### **Step 7:** The log file is stored in the file system of the server. #### **Step 8:** To get the complete path: Open the JIRA Administration go to System/System info. ![WFG_enableLog_step_8.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_26ec5bfeabb96008a8120ac7dadac7f78fc1303a4e5f4bd977cc96ee58e18d7f/WFG_enableLog_step_8.png?cb=57a0220993871e04fe3421cd7bd36d94) #### **Step 9:** Scroll down to the section "File Paths". Here you find the Location of atlassian-jira.log. ![WFG_enableLog_step_9.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_eadba3037b8be443e75df059c7a257d1f1798c6623daecbebcbb9b1a300d4b2e/WFG_enableLog_step_9.png?cb=3299cb61bc459c1701a391806dfae15b) ## Related articles --- version: "v2.0.0" language: "en" --- # End User License Agreement (EULA) End User License Agreement (EULA) for mgm Atlassian Add-Ins **Content** [1. Definitions](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/latest/end-user-license-agreement-eula.md#id-(v2.0.0)EndUserLicenseAgreement(EULA)-_Toc529728677) [2. License Version](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/latest/end-user-license-agreement-eula.md#id-(v2.0.0)EndUserLicenseAgreement(EULA)-_Toc529728678) [3. License Scope](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/latest/end-user-license-agreement-eula.md#id-(v2.0.0)EndUserLicenseAgreement(EULA)-_Toc529728679) [4. Terms of Use](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/latest/end-user-license-agreement-eula.md#id-(v2.0.0)EndUserLicenseAgreement(EULA)-_Toc529728680) [5. Intellectual Property](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/latest/end-user-license-agreement-eula.md#id-(v2.0.0)EndUserLicenseAgreement(EULA)-_Toc529728681) [6. Consideration](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/latest/end-user-license-agreement-eula.md#id-(v2.0.0)EndUserLicenseAgreement(EULA)-_Toc529728682) [7. Personal Data](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/latest/end-user-license-agreement-eula.md#id-(v2.0.0)EndUserLicenseAgreement(EULA)-_Toc529728683) [8. Update Versions](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/latest/end-user-license-agreement-eula.md#id-(v2.0.0)EndUserLicenseAgreement(EULA)-_Toc529728684) [9. Support](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/latest/end-user-license-agreement-eula.md#id-(v2.0.0)EndUserLicenseAgreement(EULA)-_Toc529728685) [10. Guarantees and Liability](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/latest/end-user-license-agreement-eula.md#id-(v2.0.0)EndUserLicenseAgreement(EULA)-_Toc529728686) [11. Publicity](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/latest/end-user-license-agreement-eula.md#id-(v2.0.0)EndUserLicenseAgreement(EULA)-_Toc529728687) [12. Confidentiality](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/latest/end-user-license-agreement-eula.md#id-(v2.0.0)EndUserLicenseAgreement(EULA)-_Toc529728688) [13. Term of the Agreement](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/latest/end-user-license-agreement-eula.md#id-(v2.0.0)EndUserLicenseAgreement(EULA)-_Toc529728689) [14. Changes to Agreement](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/latest/end-user-license-agreement-eula.md#id-(v2.0.0)EndUserLicenseAgreement(EULA)-_Toc529728690) [15. Miscellaneous Terms](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/latest/end-user-license-agreement-eula.md#id-(v2.0.0)EndUserLicenseAgreement(EULA)-_Toc529728691) [16. Data Processing Regulations](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/latest/end-user-license-agreement-eula.md#id-(v2.0.0)EndUserLicenseAgreement(EULA)-_Toc529728692) [Data Processing Addendum](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/latest/end-user-license-agreement-eula.md#id-(v2.0.0)EndUserLicenseAgreement(EULA)-_Toc529728693) ## 1. Definitions This End User License Agreement (hereinafter referred to as: "the Agreement") is between YOU, meaning your organization, represented by an authorized representative (hereinafter referred to as "User") and mgm technology partners GmbH, a private limited liability company having its principle place of business in Munich, Germany, registered with the Munich Commerce Register Court under number HRB 161298 (hereinafter referred to as "mgm"). The mgm add-ons, plugins or any other mgm products (hereinafter collectively referred to as: "Artifacts") are made available online on + and certain third party websites, hereinafter referred to as "Website". mgm may modify this Agreement from time to time, subject to the terms set out in this Agreement. ### 2. License Version This license is dated October 31^st^, 2018 and replaces all earlier versions. ### 3. License Scope mgm hereby grants the User a limited right to use the Artifacts. This license is non-exclusive and non-transferable. Only the authorized number of users may actually use the Artifacts. Additional license keys may be purchased through the Website. It is expressly forbidden to * decompile the Artifacts or to reverse engineer the source code of the Artifacts, except to the extent permitted by mandatory law or applicable open source license, * provide copies of the Artifacts to third parties, * sublicense the Artifacts or otherwise make available the Artifacts to third parties, including by rental, Software-as-a-Service models or otherwise, * modify the Artifacts, except to the extent permitted by mandatory law, * remove any indication of mgm as copyright holder of the Artifacts or to remove or render illegible any part thereof. ### 4. Terms of Use You are solely responsible for installation and usage of the Artifacts. The online available documentation will provide recommended requirements for the hardware and software environment. It is not permitted to use the Artifacts for any purpose that violates German or other applicable law or regulation. In particular it is not permitted to use the Artifacts in a manner that causes a nuisance or hindrance for other users. If in the opinion of mgm the continued functioning of the computer systems or network of mgm or third parties is under threat of being damaged or jeopardized, for example through excessive transmission of e-mail or other data, leaks of personal data or virus activity, mgm may take all steps it finds reasonably necessary to end or avert such damage or jeopardy. mgm is at all times entitled to file a criminal complaint for any offenses committed through or by using the Artifacts. In addition, mgm is entitled to supply User's name, address, IP-address and other identifying data to a third party alleging that User violates its rights or these terms and conditions, provided the validity of the complaint is clear, no other way of obtaining this information exists and the third party has an evident interest in obtaining this information. ### 5. Intellectual Property All right, title and interest to the Artifacts, the accompanying documentation and all modifications and extensions thereto belong, rest and remain with mgm. The User only has the rights and permissions explicitly granted to him by this Agreement or granted in writing otherwise. User may not use, copy, distribute or publish the Artifacts in any other manner. The Artifacts may be comprised of third-party open source software. The respective third-party right holders grant you the rights indicated in the applicable open source licenses. These licenses can be found in the documentation accompanying the Artifacts. This Agreement does not apply to this open source software, and nothing in this Agreement shall be construed as a limitation of any right granted to you under an open source license. ### 6. Consideration Unless agreed upon differently through a written contract between the User and mgm, a license for the Artifacts can only be obtained through the Website. Prices and payment details are specified on the Website. Certain Artifacts are available for a limited period at no charge. After this period a full license with a well-defined period of validity is due. This will be indicated on the Website or in the Artifacts. Prices are shown in the currency mentioned on the Website, and are shown exclusive of VAT, import duties and other government imposed taxes, duties and levies. Shortly after payment, the User may download and install the Artifacts. Prior to this, verification of the User may be required in order to ensure User is an authorized User. The Artifacts and/or the Website will inform the User of any procedures and additional conditions. ### 7. Personal Data During the installation and/or payment procedure, mgm and/or any third party processes certain of the personal data of the User. In addition to the data requested in the order form, the IP-address from which the registration is undertaken is recorded, as well as information regarding the used software. These personal data are only used for the execution of the Agreement and related purposes such as the making of related offers or notifications of available updates. For further information see the . Other terms and conditions regarding processing of Personal Data while using the Artifacts are put forward in Appendix A: the Data Processing Addendum. ### 8. Update Versions mgm may periodically release updates to or newer versions of the Artifacts that may address bugs or improve the functioning of the Artifacts. To learn about the latest versions, consult the Website regularly. No liability is accepted for any damage caused by bugs addressed in an update not installed by the User. ### 9. Support mgm shall provide the User with a reasonable level of support through the Website and e-mail or other communication channels announced to the User. mgm does not guarantee that all requests for support or bug reports are taken into consideration. ### 10. Guarantees and Liability mgm guarantees that the Artifacts substantially operate as described in the documentation; that the Artifacts contain no viruses, backdoors or malicious routines. mgm will use its best efforts to investigate any reported bugs as soon as is practical and to repair such bug or create a workaround (but may delay repairing bugs with limited impact until the next planned version), mgm grants no additional guarantees and/or warranties. In particular, mgm makes no representation or warranties, either expressed or implied, that any services rendered or any design or process which is the result of a particular use of the Artifacts, will not infringe any patent, copyright, or proprietary right of any kind of any third party, and mgm will have no liability whatsoever for any claim or suit against the User by any other party for such infringement. Except in case of intentional misconduct or gross negligence, the liability of mgm for damages in connection with the Artifacts or the violation of a warranty granted above is limited to an amount equal paid by User under the Agreement in the 6 (six) months prior to the damage-causing incident occurred. mgm in no event is liable for indirect damages, consequential damages, lost profits, missed savings or damages through business interruption. The total compensation for damages will in no case exceed the amount of EUR 500 (five hundred Euros). The obligation for mgm to pay compensation will only arise if the User sends written notice to mgm of this damage within fourteen (14) days after the damage occurring. ### 11. Publicity User hereby authorizes mgm to identify User as a customer of mgm within its promotional materials. Should User wish to object to such use, it may do so at any time by submitting an e-mail to [atlassian-info@mgm-tp.com](mailto:atlassian-info@mgm-tp.com). Please note that it may take up to 30 days to process this request. ### 12. Confidentiality Both parties shall refrain from disclosing or using for any other purpose than within the scope of this Agreement, any trade secrets and other information of the other party that has been designated as confidential or the confidential nature of which is known or can reasonably be deemed to be known by the other party. Both parties accept the duty to observe strict secrecy towards third parties with respect to all matters which have been arranged in this Agreement. In addition, the parties accept the duty to observe strict secrecy with respect to all information regarding the business, activities and organization of the other party, except in as far as such information was already part of the public domain without any involvement of the other Party. ### 13. Term of the Agreement This Agreement is entered into for the (subscription) period stated on the Website or as stated elsewhere (hereinafter: "the Contract Period"). If the Contract Period is not stipulated, it shall be deemed to have been entered into for a Contract Period of 12 (twelve) months. Unless agreed to the contrary, this Agreement, in the absence of termination in writing reaching mgm at least 2 (two) months before the end of the Contract Period, shall always be tacitly extended by the same Contract Period. mgm and/or third party will usually send User a notice for the extension of licenses and payments that may be due in that regard. This Agreement terminates automatically and immediately in case the User enters into bankruptcy, or the User applies for suspension of payments, or the assets of the User are seized, or in case the User enters into liquidation, legal dissolution or winding-up. After termination of the Agreement, regardless of the reason, User must cease all use of the Artifacts. In addition User must remove all copies (including backup copies) of the Artifacts from all computer systems under control of User. ### 14. Changes to Agreement mgm may update or modify this Agreement from time to time, including any referenced policies and other documents. If a revision meaningfully reduces User's rights, mgm will use reasonable efforts to notify User (by, for example, sending an e-mail to the billing or technical contact you designate in the applicable order, posting on our blog, through your Atlassian account, or in the Product itself). If mgm modifies the Agreement during license term and/or subscription term, the modified version will be effective upon your next renewal of a license term, support or maintenance term, and/or subscription term, whichever applies. In this case, if User objects to the updated Agreement, as your exclusive remedy, you may choose not to renew, including cancelling any terms set to auto-renew. With respect to Artifacts available for free, accepting the updated Agreement is required for you to continue using those Artifacts. You may be required to click through the updated Agreement to show your acceptance. If you do not agree to the updated Agreement after it becomes effective, you will no longer have a right to such Artifacts. For the avoidance of doubt, any order is subject to the version of the Agreement in effect at the time of the order. ### 15. Miscellaneous Terms German law applies to this Agreement exclusively. Unless dictated otherwise by mandatory law, all disputes arising in connection with this Agreement shall be brought before the competent German court for the principal place of business of mgm which is in Munich. A finding that any particular provision of this Agreement is legally void or unenforceable shall not affect the validity of the entire Agreement. In such a case the parties shall determine a replacement provision that is legally valid and approximates the intent of the relevant provision as much as possible. mgm may assign its rights and obligations under this Agreement to a third party that acquires the relevant business or the copyrights to the Artifacts from her. ### 16. Data Processing Regulations It is possible that by using the Artifacts, the End User processes personal data and therefore, that mgm processes that personal data on behalf of the End User, especially in cases of analyzing problems via log files or alike. In that case, the following articles apply, complementary to the Agreement and the Privacy Policy. The applicability of any data processing agreement or addendum preceding this data processing addendum or issued by the End User is strictly rejected. Appendix A: ### Data Processing Addendum #### Introduction and definitions 1. The word "End User" as applied in this Data processing addendum means your organization, represented by an authorized representative. The word "End Users" as applied in this data processing addendum means any individual in or represented by your organization that uses the Artifacts, either as an administrator or a user. 2. Definitions that are used in this data processing addendum derive their meaning from their definitions as meant in the EU General Data Protection Regulation (GDPR). 3. This Data Processing Addendum qualifies as a data processing agreement as described in Article 28 GDPR. 4. If the End User processes personal data by using the Artifacts, mgm processes such personal data on behalf of the End User. Consequently, the End User and mgm agree that the End User is regarded as the data controller and mgm is regarded as the data processor. Alternatively, if the End User is processing personal data on behalf of a third party, the End User is regarded as the data processor and mgm is regarded as the data sub-processor. ##### Description of Data Processing 1. mgm commits to process personal data on behalf of the End User, under the conditions of the Agreement, which reflect the written instructions by the End User for the processing of personal data. mgm will solely process the personal data in the context of the Agreement and the Privacy Policy, their duration and purpose, and other purposes that can reasonably be associated with their purpose or purposes that are to be defined under future consent. 2. mgm will not process the personal data for purposes different from the purposes as set forward in the Agreement and the Privacy Policy. The End User will inform mgm of purposes for the processing of personal data that are not yet mentioned in the Agreement. 3. mgm has no saying in the purpose and means of the processing of the personal data. Additionally, mgm has no saying in the nature of the personal data that is processed. All personal data processed in connection with the Artifacts shall deemed to have been processed at the instructions of the End User. 4. mgm will not make independent decisions about the data gathering and use of the personal data, the provision to third parties, the duration and the storage of the personal data. 5. The personal data are related to the following data subject categories: 1. People who use the Artifacts (the End Users); and/or 2. People whose personal data is captured or processed in the Artifacts by End Users; and/or 3. People whose data is transmitted via the Artifacts by End Users; and/or 4. Other possible data subject categories whose personal data is processed using the Artifacts. ##### Non-disclosure and Confidentiality 1. mgm is bound to non-disclosure against third parties for all personal data that mgm processes on behalf of the End User, following from this Data Processing Addendum. mgm will not use this data for any other purpose than for which mgm received the data from the End User, except if the data is altered (encrypted or a anonymized) in such a way that it is no longer traceable to an individual data subject. 2. The non-disclosure as meant in DP-3 section 1 is not applicable: 1. to the extent that the End User has provided mgm the permission to provide the data to third parties; or 2. when the provision of the data to third parties is logically necessary for the use or proper functioning of the Artifacts or the execution of this data processing addendum; or 3. if a legal requirement or court order exists to provide the data to third parties; or 4. in regard of third parties to which personal data are provided in their role as sub-processor, taking into account the conditions defined in ‎DP-5. ##### Security and Technical and Organizational Measures 1. With regard to the processing of personal data, mgm will strive to take adequate technical and organizational measures, in particular to safeguard against the destruction, loss, mutation or unauthorized provision or unauthorized access to transferred, stored or otherwise processed personal data. 2. The technical and organizational measures that mgm takes follow from the most recent version of their information security policy can be provided by mgm upon justifiable request. 3. In case, in mgm's opinion, this is necessary to offer a continued adequate level of security, mgm is allowed to make changes to the security measures. 4. mgm does not guarantee that their security is effective under all conditions. mgm will strive to maintain a reasonable level of security, taking into account the state of technology, implementation costs of the security measures, the nature, extent and context of the processing of personal data, the purposes and the intended use of the Artifacts, the data processing risks and the risks for the rights and freedoms of data subject, which they may have expected considering the intended use of the Artifacts and which are divergent for their probability and impact. 5. The End User asserts that the security measures as meant or referred to in ‎DP-4, considering the factors as described herein, provide an adequate level of security that is in accordance with the risks of the processing of personal data processed by or provided by the End User. 6. The End User will only provide personal data for processing to mgm if the End User has ensured themselves that the required security measures are taken. The responsibility for the compliance of the measures as agreed between the End User and mgm resides with the End User. ##### Sub-Processors 1. The End User provides mgm the general permission to work with third parties (sub-processors) for the processing of personal data. mgm always work with their associated companies in the European Union and in countries outside of the European Union, while taking into account relevant laws and regulations. 2. Upon request by the End User and within a reasonable time frame, mgm will inform the End User about the relevant third parties that mgm works with, regarding the processing of the personal data as meant in this data Processing Addendum. 3. mgm has the right to add or replace third parties (changes). If mgm intends to add or replace a third party, mgm will inform the End User accordingly, allowing the End User to object. If the End User wishes to object, the End User must submit their objection in written form, within two weeks and supported by sound argumentation. If the End User does not object within these conditions, the End User is regarded to accept the intended change. 4. If the End User objects within the conditions as stated above in ‎DP-5 section ‎2, mgm and the End User will consult each other and strive to achieve a reasonable solution. If both parties cannot achieve a satisfactory agreement about the intended change as meant above in ‎DP-5 section ‎2, mgm is entitled to work with the respective added or replaced third party. Respectively, the End User is entitled to terminate their subscription to the Artifacts per the date that the new sub-processor is activated. 5. At all times, mgm ensures that the third parties as meant in this article will take on the same obligations as agreed between the End User and mgm in writing and ensures the compliance by these third parties of these obligations. ##### Transfer of Personal Data 1. mgm processes personal data in countries of the European Union. Additionally, the End User permits mgm to process personal data in countries outside of the European Union, while taking into account relevant laws and regulations. 2. Upon request and within a reasonable time frame, mgm will inform the End User in which countries mgm processes the personal data. ##### Data Subject Rights and Requests 1. If a data subject submits a request about their personal data to mgm in order to exercise their data subject rights, mgm will forward the request to the End User and inform the data subject accordingly. The responsibility for processing the request and performing data subject rights lies with the End User, who will process the request and perform the data subject rights independently from mgm. 2. mgm will provide assistance to the End User for processing a request by a data subject and performing their data subject rights, should this occur to be necessary. mgm may charge the End User for reasonable expenses that are made or to be made while providing such assistance, which will be reimbursed by the End User. ##### Obligations and Support 1. mgm will commit to compliance with the conditions that, based on the GDPR, are bound to the processing of personal data by mgm in their specific role, regarding the processing of personal data as meant in ‎DP-2 of this data processing addendum. 2. mgm will process personal data and other forms of data that are made available to mgm by the End User based on written instructions by the End User. 3. Upon request and within a reasonable time frame, mgm will inform the End User about the (technical and organizational) measures taken by mgm to comply with their obligations as meant under this data processing addendum. 4. The obligations as meant in this data processing addendum are also applicable to parties that process personal data under mgm's authority. 5. If, in mgm's opinion, an instruction given by the End User is conflicting with relevant laws and regulations, mgm will inform the End User. 6. At the request of the End User, mgm will, within a reasonable time frame, provide the End User with the necessary cooperation to meet their compliance with the obligations that follow from the GDPR. This includes, among others, their obligations with regard to data security, reporting personal data breaches and performing data protection impact assessments. mgm will charge the End User for reasonable expenses that are made or to be made while providing such cooperation, which will be reimbursed by the End User. ##### Personal Data Breaches 1. A personal data breach is defined as a violation of security that accidentally or unlawfully leads to the destruction, loss, mutation or the unauthorized provision or unauthorized access to transmitted, stored or otherwise processed personal data. 2. If a personal data breach occurs, mgm will inform the End User to the best of their abilities, abiding by applicable laws and regulations. The End User will then judge if they need to inform the supervisory authorities and/or data subjects. mgm strives to ensure that the information is complete, correct and accurate to the best of their abilities. 3. mgm will cooperate with informing the relevant authorities and, if required, the data subjects, should this be required by any law or regulation. The responsibility for informing the relevant authorities and the data subjects resides with the End User. 4. If a personal data breach has occurred, mgm will provide the following information to the End User: 1. The fact that a personal data breach has occurred 2. the (supposed) cause of the breach 3. the (then known or expected) effects 4. the (proposed) resolution 5. the taken measures 6. the contact details for the follow-up of the issue 7. an overview of the informed parties (e.g.: the data subjects) ##### Destruction or Return of Personal Data 1. After termination of this data processing addendum, mgm will destroy the personal data it has received from the End User without delay, except if mgm and the End User agree that mgm will return the personal data to the End User or retain the personal data for an agreed period, or if mgm is required by law to retain the personal data. 2. mgm may charge the End User for reasonable expenses that are made or to be made for the destruction or the return of the personal data to the End User, which will be reimbursed by the End User. ##### Audits 1. For the verification of compliance of all items from this data processing addendum, the End User has the right to issue audits by a competent and independent party. 2. This competent and independent party is bound to non-disclosure. 3. An audit will only be conducted after the End User has requested the available similar audit reports from mgm, has judged the reports and provides sound argumentation why an audit, initiated by the End User, is still justifiable. Such an audit will only be justifiable when the similar audit reports that are available from mgm provide no or insufficient proof about the compliance of this data processing addendum by mgm. If an audit, initiated by the End User, is justified, it will only be conducted at least 30 days after prior announcement by the End User, with a maximum of once per year. 4. mgm will cooperate with the audit and will provide all information that is reasonably relevant for the audit, including supportive information such as system logs and access time to relevant employees, as timely as possible and within a reasonable time frame (within two weeks or sooner in case of an urgent interest). 5. In mutual consultation, the End User and mgm will judge the findings that may result from the audit. As a result of this process, measures may be implemented by either mgm, the End User or both parties. 6. Reasonable expenses made or to be made by mgm in this process will be reimbursed by the End User. The expenses for the hired competent and independent party are always the responsibility of the End User and will be met by them. ##### Distribution of Responsibilities 1. Both mgm and the End User commit to compliance with applicable laws and regulations. mgm performs the processing of personal data under the scope of the Agreement and the Privacy Policy in a (semi)automated environment. 2. mgm is only responsible for the processing of personal data as meant in this data processing addendum, abiding by the instructions of the End User and under the explicit (final) responsibility of the End User. 3. mgm is not responsible for all other processing of personal data, including but not limited to the collection of personal data by the End User, processing of personal data for purposes that the End User failed to report to mgm, processing by third parties and processing for other purposes. For such processing of personal data, the End User has the exclusive responsibility. At all times, the End User guarantees the legality of their processing of personal data and the adequacy of the security of their systems and infrastructure. 4. The responsibility for judging whether mgm offers adequate safeguards regarding the implementation of technical and organizational measures in order for the processing of personal data to be compliant with the demands from the GDPR and/or other applicable laws and regulations and whether the protection of the rights of the data subjects is adequately safeguarded, lies with the End User. 5. At all times, the End User guarantees that the content, use and instructions for the processing of personal data as meant in this data processing addendum is not unlawful and does not infringe any rights of third parties. 6. Notwithstanding other rights of mgm, the End User safeguards mgm from all legal claims by third parties, from any source, if the legal claim relates to the processing of personal data. Additionally, the End User safeguards mgm from potential damages and fines, imposed by competent supervisory authorities, for which the End User is accountable and/or if the End User violates this data processing addendum, the GDPR or any other applicable laws and regulations. ##### Duration and Termination 1. The duration of this data processing addendum is identical to the duration as defined in the Agreement or contract that is agreed upon between mgm and the End User. If there is no duration defined in any of these documents, the duration of this data processing addendum is identical to the duration of the collaboration between the End User and mgm. 2. This data processing addendum cannot be terminated intermediately. 3. ‎‎DP-3 (Non-disclosure and Confidentiality) will survive the termination of the data processing addendum. 4. mgm and the End User may only change this data processing addendum with mutual consent. --- version: "v2.0.0" language: "en" --- # FAQ --- version: "v2.0.0" language: "en" --- # Introduction ## Problem *** ** * ** *** A workflow diagram provides a graphic overview of the issue-type process. It should help project members to understand their roles and the order in which the issues are completed. Using own design like symbols and shapes to show step by step how the issue is completed from start to finish, showing conditions and rules or showing who is responsible for work at what point in the process are requirements that are not included in Jira inbox workflow editor. It is comprehensible that the customer wants to use his own vitalization tool. The question is how to replace standard Jira workflow diagrams and use your customized graphics in Jira. ## Solution *** ** * ** *** **Link Workflow Graphic for JIRA** Prepare your workflow graphics with your favorite editor and use your own design. Visualize conditions and rules which you implemented in your Workflow into your graphic. Show addition details and information about the process in the graphic. Design your graphics depended on user language. Finally, as an Administrator use **Link Workflow Graphic for Jira** add-on to replace JIRA standard graphics. Upload and configure your customized workflow graphic into JIRA. To find out how to install, configure and use this add-on follow the links in the left navigation. ![WFG_viewWF_1840x900px 3.jpeg](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_af0bf5ed80d21f99998311f542a51721e088efc0422b4582d8685dc9d8093ea4/WFG_viewWF_1840x900px%203.jpeg?cb=25fe538f9c4fe72714edc74e4e251124) ![2018-11-WFG-Plugin-Logo-144px.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_32bfa88bec0c3c0a555a3bc9353e9175e5b63d6a8deea12f44ed3a773fa9b2e7/2018-11-WFG-Plugin-Logo-144px.png?cb=dc3866c0002563c237664d33a3cefc59) [https://marketplace.atlassian.com/apps/1219912/link-workflow-graphic-for-jira?hosting=server\&tab=overview](https://marketplace.atlassian.com/apps/1219912/link-workflow-graphic-for-jira?hosting=server&tab=overview) **The current version is 1.1.2** --- version: "v2.0.0" language: "en" --- # License --- version: "v2.0.0" language: "en" --- # Release Notes ## This page lists the release notes from all versions of Link Workflow Graphic for JIRA. ## **2.0.0 (April 29, 2025)** ### **Compatibility** * **Jira Data Center 10.0.0 - 10.3.5 compatibility** *** ** * ** *** ## **1.2.4 (May 22, 2024)** ### **New Features** * Sorting in Workflow Graphics view and Project Configuration view * Filter in Workflow Graphics view and Project Configuration view #### **Bug Fixes** * Fixed bug cannot view workflow in Queue Issue View (Jira Service Management) *** ** * ** *** ## **1.2.3 (Jan 26, 2024)** ### **Bug Fixes** * Fixed bug cannot show graphic in "View workflow" button in Jira 9 *** ** * ** *** ## **1.2.2 (Aug 29, 2022)** ### **Bug Fixes** * Fixed bug cannot access app UI due to some methods are not allowed in Jira version 9.4.9 *** ** * ** *** ## **1.2.1 (Jul 26, 2022)** ### **Compatibility** * Jira Data Center 7.0.0 - 9.10.0 compatibility *** ** * ** *** ## **1.2.0 (Jun 29, 2022)** ### **Upgrade** * Add maven dependency check #### **Compatibility** * Jira 8.22.4 compatibility * Jira DC compatibility *** ** * ** *** ## **1.1.6 (Apr 14, 2021)** ### **Bug Fixes** * Fixed bug where the unmapped graphic will always select to use, even when you have the graphic configured for your language #### Compatibility * Jira 8.16.0 compatibility *** ** * ** *** ## **1.1.5 (Otc 16, 2020)** **Compatibility** * Add JIRA 8.7.1 Compatibility *** ** * ** *** ## **1.1.4 (Feb 18, 2020)** **Compatibility** * Add JIRA 8.7.1 Compatibility *** ** * ** *** ## **1.1.3 (Jan 10, 2020)** ### **Bug Fixes** * Fixed bug: App can't work with OracleDb * Add more validation **Compatibility** * Add JIRA 8.5.1 Compatibility - fix UI *** ** * ** *** ## **1.1.2 (Sep 03, 2019)** ### **Bug Fixes** * Fixed bug can't import the backup XML file **Compatibility** * Add JIRA 8.3.3 Compatibility *** ** * ** *** ## **1.1.1 (Jan 04, 2019)** ### **Bug Fixes** * Fixed bug the graphic cannot be shown in a new popup in View All Issue page * Fixed text error in add-on banner *** ** * ** *** ## **1.1.0** **(****Dec 21, 2018)** ### **New Features** * Added license system, this add-on is no longer free * Added upload option when adding a graphic, now you can either use a graphic URL or simply upload it from your computer * Added support for use already uploaded graphics as new Graphic Language Entry, so now you have three options when creating a Graphic: use an image URL from internet, upload one from your computer, or choose an existed image in your Jira system * Removed graphic sizing option. All graphic now have no sizing option, it will automatically display with original size, with the ability to resize dynamically * Added Graphic Management. From now on, you can manage all graphic on your system. You can name the graphics, write a description, see where those graphics are used, view details of graphic. And you can delete the graphics that are no longer used * Added logging details for debug level to better troubleshooting for customers #### **Bug Fixes** * Fixed graphic is not shown when the URL is wrong or dead * Fixed the detail module is duplicate in issue view page * Fixed error messages always appear for the first time you associate project to workflow graphic scheme * Fixed broken table when line was too long *** ** * ** *** ## **1.0.2 (Aug 13, 2018)** * Initial release core features *** ** * ** *** ### Semantic Versioning: Given a version number MAJOR.MINOR.PATCH, increment the: * MAJOR version when incompatible API changes are made * MINOR version when functionality in a backward-compatible manner is added * PATCH version when the backward-compatible bug is fixed --- version: "v2.0.0" language: "en" --- # Restore from Backup The page "**Restore Project Workflow Graphic Configurations"** provides you the ability to restore all your configuration from the XML file. Backups should always happen first! * [Create Backup](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/latest/create-backup.md) Old data will be cleaned before the restore process. Old data will be cleaned before the restore process. ![https://wiki.mgm-tp.com/confluence/download/attachments/128853296/WFG_restore_1840x900px.png?api=v2](https://wiki.mgm-tp.com/confluence/download/attachments/128853296/WFG_restore_1840x900px.png?api=v2) --- version: "v2.0.0" language: "en" --- # Support Please use one of the following channels for any issue, question or suggestion: |------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| | **Service Desk** | [Support Service Desk](https://mgm-tp.atlassian.net/servicedesk/customer/portal/2) ( ) | | Email | [atlassian-info@mgm-tp.com](mailto:atlassian-info@mgm-tp.com) | ## Business Hours Monday - Friday from 09:00 - 17:00 UTC+2. ## Response Times Expect a response to **support requests** created via the Service Desk portal described above within 1 business day (24 hours). Please don't hesitate to contact us via other channels if you do not receive a timely response! ![59c9902f-84f1-4e66-a247-c3edf7140ff2.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_c5bd01a3224ab88477acfd3ac673a930add9cec6749a286ac2c8e76cbfc4ad2c/59c9902f-84f1-4e66-a247-c3edf7140ff2.png?cb=3571bfef4b5b5d875a18f070ef600fe5) **Company** **mgm technology partners gmbh** Frankfurter Ring 105a 80807 München Germany --- version: "v2.0.0" language: "en" --- # Troubleshooting Articles * [Enabling logging for "Link Workflow Graphic for JIRA" plugin](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/latest/enabling-logging-for-link-workflow-graphic-for-jir.md) --- version: "v2.0.0" language: "en" --- # User Guide ## Everything you may want to know before using the "Link Workflow Graphic for JIRA": To implement the Workflow for your process, just ask your JIRA Administrator. Visualize this workflow with our own editor and customize your graphic. If you want to use different Jira user languages prepare your graphic in those languages. To configure a Workflow Graphic for your project, contact your Jira Administrator and provide them with the file of graphics or URLs of those graphics. Once everything is configured, go to any issue in the project that has an assigned graphic. To see your custom workflow, click "View Workflow" and a new popup window will come up. You can use your mouse to adjust the size of the workflow. ![WFG_viewWF_1840x900px 3.jpeg](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_e2d0a99d2b42249a6828762eee6c18a8bb2ff62d577133d44d637597c51ab57e/WFG_viewWF_1840x900px%203.jpeg?cb=25fe538f9c4fe72714edc74e4e251124) --- version: "v1.2.0" language: "en" --- # Link Workflow Graphic for Jira ## Documentation * ### [Introduction](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/v1.2.0/introduction.md) * ### [Download \& Installation](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/v1.2.0/download-installation.md) ### [Administrator Guide](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/v1.2.0/administrator-guide.md) * ### [User Guide](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/v1.2.0/user-guide.md) ### [License](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/v1.2.0/license.md) * ### [Release Notes](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/v1.2.0/release-notes.md) ### [Troubleshooting Articles](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/v1.2.0/troubleshooting-articles.md) * ### [Support](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/v1.2.0/support.md) * ### [FAQ](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/v1.2.0/faq.md) --- version: "v1.2.0" language: "en" --- # Administrator Guide ## Preconditions *** ** * ** *** * **Link Workflow Graphic for Jira**Add-on is already installed on your JIRA server with a license or trial license * You must be logged in as a user with the **JIRA Administrators** [global permission](https://confluence.atlassian.com/adminjiraserver/managing-global-permissions-938847142.html) ## Step by step guide *** ** * ** *** Here are the exact steps you should take to setup a Workflow Graphic. Click on the links to get to the detailed introduction. 1. [Create a Graphic Language Scheme](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/v1.2.0/configure-graphic-language-schemes.md) 1. Add a graphic 2. Associate it with a language 2. Create a [Workflow Graphic Scheme](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/v1.2.0/configure-workflow-graphic-scheme.md) 1. Associate a workflow with the *Graphic Language Scheme* set in previous step 3. [Associate your project](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/v1.2.0/configure-project.md) with the Language Scheme set in previous step ## Backup and Restore configurations *** ** * ** *** ## Backup **Link Workflow Graphic for Jira** provides the ability to back up all your configuration for "Link Workflow Graphic for JIRA" add-on. Go to [Create Backup](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/v1.2.0/create-backup.md) for more information. ## Restore To find out how to restore Workflow Graphic configuration from a backup follow this [link](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/v1.2.0/restore-from-backup.md). --- version: "v1.2.0" language: "en" --- # Configure Graphic Language Schemes ## Step by step guide *** ** * ** *** 1. Click the cog icon ![https://confluence.atlassian.com/adminjiraserver/files/951394526/951394527/1/1527598493234/cog_icon.png](https://confluence.atlassian.com/adminjiraserver/files/951394526/951394527/1/1527598493234/cog_icon.png) and choose **Add-ons** from the drop-down menu ![image2018-12-19_14-40-54.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_c20fc28b5ec3fcd9ac3d80c12419e9aace8a45a2b147cc88e04f6fcb53cf8b74/image2018-12-19_14-40-54.png?cb=100cd1a5932288b5de86c9223773021f) 2. Go to the **Add-ons Administration** page. On the left side of this page, under**WORKFLOW GRAPHICS** section, select **Graphic Language Schemes** ![image2018-12-20_14-45-33.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_9de98b512ddec0cc8b18a90fafe41444a0bed194c7b2adb3a28e38466fe97bd4/image2018-12-20_14-45-33.png?cb=ecdd268c24efc674c0f02df38213e82c) 3. In **View Graphic Language Schemes** page, click ![image2018-12-20_14-56-2.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_cb15f42c6e785615590611c1219af96aa3e21eb4e1ba958fb455e0bce4b9358e/image2018-12-20_14-56-2.png?cb=f57d3764a1d9669552bfc084c1b4f188) . 4. In the popup window, enter the name and description for your scheme, and then click **Add** . Note that the name field is required, the description is optional. ![image2018-12-20_15-9-51.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_2f753644dcd50fa5cd88c3763997c296bcfcab1b8de3da2a34d144a59fc23f06/image2018-12-20_15-9-51.png?cb=10953bd23b32355a9e82da9aaa84ba11) Once the creation successfully, you will be redirected to **Configuration Graphic Language Scheme** page, with your scheme name on the title. ![image2018-12-20_15-15-5.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_022b5f87b8668eab438a6bd171292949788b74f0a2fbb68d89ebf69a5e18f8c5/image2018-12-20_15-15-5.png?cb=8f3d57f11feb7a278639aa1920974a3c) 5. Click on the ![image2018-12-20_16-30-48.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_78a192b84b1e5dd38359ae8cf78f9d307c9af7a81471ee4332a91eb04e8cdae4/image2018-12-20_16-30-48.png?cb=0ae4004779a7252d166ec79c5484beb0) to go to **Add Graphic Language Entry** page, here you can associate your graphic with a language. ![image2018-12-20_16-35-36.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_a726bd7d87a672f5d45854ffb9551920a788a98eb71917476e5ff0dd60434f99/image2018-12-20_16-35-36.png?cb=5cc23c91418cb9ebd8818a0d3eeb6352) Here you have 3 options to add a graphic: + Use an URL + Upload an image from your computer + Choose one from all existed graphics After choosing a language and specifying the graphic, click **Add** . If successful, you will be directed back to the **Configuration Graphic Language Scheme** page, where you should see your new entry in the list ![image2018-12-20_16-43-36.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_e35d0d489ab44baefc8d9df22db15bd9730cef8a64f79a9d3f6f8a01f8a6d790/image2018-12-20_16-43-36.png?cb=390878eb9b8f614ff173f3b152e61dba) 6. Go back to **View Graphic Language Schemes** page by clicking again on **Graphic Language Schemes** on the left navigation. Your scheme should be seen in the list. ![image2018-12-20_16-50-43.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_4966f5c176ef616e824a0bf932046a0b825dc432450d6581ffc8a556f68fc665/image2018-12-20_16-50-43.png?cb=ff7a25e09912cf7ade717ddc1530e338) You are done with **Graphic Language Scheme** configuration. --- version: "v1.2.0" language: "en" --- # Configure Project ## Step by step guide *** ** * ** *** 1. Go to **Add-ons** page as step 1 at [Configure Graphic Language Schemes](https://mgm-tp.atlassian.net/wiki/pages/resumedraft.action?draftId=86638607#AdministratorGuide-ConfigureGraphicLanguageSchemes) 2. In **Add-ons** page, click on the link **Project Configurations** under **Workflow Graphic** section. You will go to **View Project Workflow Graphic Configurations** page, where you will see a list of projects you have. ![image2018-12-20_17-41-40.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_73ab90a083838961f0a94f54fa94905b434d0aad159f48466372bb30bd2755fa/image2018-12-20_17-41-40.png?cb=e060ea60ea81dd029c8fdf1dc109acad) 3. Click **Edit** on the project that you want to configure. Next, go to the **Edit Project Association** page and decide if you want to use a standard workflow of Jira for your project or use your custom workflow by check or uncheck the checkbox **Standard Workflow.** If the checkbox **Standard Workflow** is unchecked you will see a list of all already existing **Workflow Graphic Scheme** by expanding the content of the field "**Workflow Graphic Scheme** ". Choose your target **Workflow Graphic Scheme** to assign it to your project. Then click **Update** ![image2018-12-20_17-51-18.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_d60c5d2a33e613769cecdcdb45551ffb96e4bf5d92a9658f5c22fdb23d280fdd/image2018-12-20_17-51-18.png?cb=3d3d6cdaa4417354c0e60c3826c34c23) Now you should be sent back to the **View Project Workflow Graphic Configurations**page and you should see your project is in the configuration you made. ![image2018-12-20_17-54-14.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_3273e1a83b11ab93742fa1a0befce44c56b20eaa7ef10ed4f936515851b4f882/image2018-12-20_17-54-14.png?cb=a75ab35148f03234a7b59f1374cea073) You are now done with the **Configure a Workflow Graphic** for the project. Next, you will be shown how to backup and restore your configuration. --- version: "v1.2.0" language: "en" --- # Configure Workflow Graphic Scheme ## Step by step guide *** ** * ** *** 1. Go to **Add-ons Administration** page and click on [Configure Graphic Language Schemes](https://mgm-tp.atlassian.net/wiki/pages/viewpage.action?pageId=86606134) 2. On the left navigation, under**WORKFLOW GRAPHICS** section, select **Workflow Graphic Schemes** to go to the **View Workflow Graphic Schemes** page ![image2018-12-20_17-10-9.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_3279c88f4f5cff112bc7f80e3c8e26e94a78cd3bbe3a835d749f7912698b66cd/image2018-12-20_17-10-9.png?cb=41ccaa6c74c51fdb634ddc1fefab8b3c) 3. Click on the button ![image2018-12-20_17-11-23.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_5a9e2b8baca624c84bd8697aa9b011dd15eaa7e311885f3fd6e57a60a3f00dbf/image2018-12-20_17-11-23.png?cb=bb902c5db11152b2cbcd64140f2f2d74) 4. On the **Add Workflow Graphic Scheme** popup window, enter name (required) and description of your scheme. Then click **Add.** ![image2018-12-20_17-15-13.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_5f9858d1cfbec8b9d4e4a7bfe81427ba8d16e11be485c5421f7c8ba3508e999e/image2018-12-20_17-15-13.png?cb=cd15030131fe642af867c47da68c59a9) Once the creation successfully, you will be redirected to **Configuration Workflow Graphic Scheme** page, with your scheme name on the title ![image2018-12-20_17-18-1.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_b0d45232fe904d6a210413798063ccce33bf7a031fa1c2133342474cd6613347/image2018-12-20_17-18-1.png?cb=da552a57f0a28f9f7659730d40d6a9ac) 5. Click on the ![image2018-12-20_17-18-46.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_3a35c26477bd9ed48293b3e42d4e19ae1826e6c2112087fc0c4b10a3919a732c/image2018-12-20_17-18-46.png?cb=8cc7700fa9ae87391b1a373294cbe917) to map your Graphic Language Scheme with any standard Jira Workflow. In the popup window, choose the Jira workflow that you want to be replaced by your**Graphic Language Scheme** then click **Add** . ![image2018-12-20_17-25-36.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_3b5bb838a48e586daa934b3f76de837a72dad9a19e9e747570dd6aeec4d7e224/image2018-12-20_17-25-36.png?cb=beeb1d8c7a01a9c4a8df1b5f802ca4a1) If it is successful, the popup will disappear, and you will see a new config added to the list. ![image2018-12-20_17-29-53.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_e2a7f8d5d5dbce72f0fafc30fce9c9693bcd0d9dfec24cdc870c295580cd70e8/image2018-12-20_17-29-53.png?cb=eafecf24e4ebb7655a672e0de16da9d1) 6. To go back to **View Workflow Graphic Schemes** page, click again on **Workflow Graphic Schemes** on the left navigation. Your scheme should be placed in the list now. ![image2018-12-20_17-32-11.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_c914f579d959e1c5405e86bb0e2612b2672f56c787405319dfc9c7609ce7786b/image2018-12-20_17-32-11.png?cb=332258780fd0d41f3900f39660a96d18) You are done with the configuration of **workflow graphic scheme** and can use it in your project. The next step is to associate this **workflow graphic scheme** with your project. --- version: "v1.2.0" language: "en" --- # Create Backup This page describes how to back up your **Workflow Graphic** data. You need to create a back up if you plan to upgrade your server to a new Jira revision or split your Jira instance. To create a backup follow the steps below. * Choose ![https://confluence.atlassian.com/adminjiraserver/files/951394526/951394527/1/1527598493234/cog_icon.png](https://confluence.atlassian.com/adminjiraserver/files/951394526/951394527/1/1527598493234/cog_icon.png) **\>** **Add-ons**. * Select **WORKFLOW GRAPHICS \> Backup CONFIGURATION**to open the Backup Workflow graphic data page. ![https://wiki.mgm-tp.com/confluence/download/attachments/128853296/WFG_backup_1840x900px.png?api=v2](https://wiki.mgm-tp.com/confluence/download/attachments/128853296/WFG_backup_1840x900px.png?api=v2) The location of workflow graphics XML backup is displayed on this page. The location of workflow graphics XML backup is displayed on this page. * Type the name of the backup file in the **"File name"** field Ensure that Jira has the necessary file system permissions to write to this location. * Click the **'Backup'** button and wait while your Jira data is backed up. * When the backup is complete, a message will be displayed, confirming that Jira has written its data to the file you specified. --- version: "v1.2.0" language: "en" --- # Download \& Installation ## Preconditions *** ** * ** *** * You must be logged in as a user with the **JIRA Administrators** [global permission](https://confluence.atlassian.com/adminjiraserver/managing-global-permissions-938847142.html) ## Download and install *** ** * ** *** ### Download the add-on directly from Atlassian Marketplace 1. Click the cog icon ![image2018-12-19_14-52-42.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_80f804a6d96c4f53dd013d953a2187059e08b17167ac512dfcec40179873c2ec/image2018-12-19_14-52-42.png?cb=e75492c19448d6d85bb7792ae72bacb8) and choose **Add-ons** from the drop-down menu ![image2018-12-19_14-40-54.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_f54a8bb770f64733e294b8a9442bb0ab6bb9a814319c90a4ace6ecbadf204bc8/image2018-12-19_14-40-54.png?cb=100cd1a5932288b5de86c9223773021f) 2. You will be redirected to **Atlassian Marketplace for JIRA** page. In the **Search the Marketplace** box, enter "**Link Workflow Graphic for JIRA** " then press Enter ![image2018-12-19_15-0-52.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_fa5e6879b36ef9c64d36f890a090507b4006dc423b507a6f1d627450948f0483/image2018-12-19_15-0-52.png?cb=2b783f85c704db630aa0c66c2ca051f0) 3. In the search result list, you should see a plugin called **Link Workflow Graphic for Jira.** Click **Buy now** (or **Free trial** if you want a 30-day trial version). ![image2018-12-19_15-12-49.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_913a9373189417e4f1ec8e4ffcdc0e72dc90e0b2023a24199c869145793f56f4/image2018-12-19_15-12-49.png?cb=394b7701d1ac6263bdadc541d314521e) 4. Once the purchase process is completed, the plugin will install automatically ![image2018-12-19_15-18-42.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_0f5f4e7f33ea574d5d78977a53592acaf5bc4e96a7b8a7ab6ab90897d18f3ddb/image2018-12-19_15-18-42.png?cb=8f5264983d926932b4e9520ce8af4983) 5. Add-on **Link Workflow Graphic for JIRA**will be displayed under **User-installed add-ons** ![https://mgm-tp.atlassian.net/wiki/download/attachments/86540302/WFG_Download&Install_step_6.png?version=1&modificationDate=1544785196959&cacheVersion=1&api=v2&height=400](https://mgm-tp.atlassian.net/wiki/download/attachments/86540302/WFG_Download&Install_step_6.png?version=1&modificationDate=1544785196959&cacheVersion=1&api=v2&height=400) 6. For further licensing and purchasing information check the link [**License**](https://mgm-tp.atlassian.net/wiki/spaces/HCF/pages/73728004/License)in the left navigation --- version: "v1.2.0" language: "en" --- # Enabling logging for "Link Workflow Graphic for JIRA" plugin ## Problem Logging can be useful in diagnosing problems when the cause is not clear. If a Problem occurs in our add-on, you can send us your JIRA Log file. Logging can be useful in diagnosing problems and helps us to solve the problem faster. This How-To describes the steps to create the required log files. ## Precondition You must be logged in as a user with the **JIRA Administrators** [global permission](https://confluence.atlassian.com/adminjiraserver/managing-global-permissions-938847142.html) ## Solution ### **Step 1:** Go to JIRA **Administration** \>**System** \>**Logging and profiling** ![EnabeLogging_step_1.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_9114e453e36634d988ef456b7909e8780c2a9f0b94182d8b4cb19291184081f2/EnabeLogging_step_1.png?cb=ccbfd241f6e40f0961e4a6f9e40e61b3) #### **Step 2:** Under Default Loggers, click "**configure logging level for another package** " #### **Step 3:** For Package name enter com.mgmtp.jira.plugin.workflowgraphic #### **Step 4:** For Logging Level select **DEBUG** #### **Step 5:** Press **Add** to save ![WFG_enableLog_step_2_3_4_5.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_875ec769804cc281d18cfceaff54880bda7e6a0575617219aaddd80bbddf745b/WFG_enableLog_step_2_3_4_5.png?cb=a36cbff3cf36741f975795bdd3adadb7) #### **Step 6:** "Link Workflow Graphic for JIRA" plugin log output will now be added to JIRA's own `atlassian-jira.log` file #### **Step 7:** The log file is stored in the file system of the server. #### **Step 8:** To get the complete path: Open the JIRA Administration go to System/System info. ![WFG_enableLog_step_8.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_c20f5186a1efaef80af5b52aa8c6e9831a3d7d5677d55170f6267f145e5c97cc/WFG_enableLog_step_8.png?cb=57a0220993871e04fe3421cd7bd36d94) #### **Step 9:** Scroll down to the section "File Paths". Here you find the Location of atlassian-jira.log. ![WFG_enableLog_step_9.png](https://mgm-atlassian-apps.mgm-tp.com/__attachments/a_f4a3e743590b4495f66ffc38ea6a6015456e956090d33772f71ba6d7109dfa5f/WFG_enableLog_step_9.png?cb=3299cb61bc459c1701a391806dfae15b) ## Related articles --- version: "v1.2.0" language: "en" --- # End User License Agreement (EULA) End User License Agreement (EULA) for mgm Atlassian Add-Ins **Content** [1. Definitions](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/v1.2.0/end-user-license-agreement-eula.md#id-(v1.2.0)EndUserLicenseAgreement(EULA)-_Toc529728677) [2. License Version](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/v1.2.0/end-user-license-agreement-eula.md#id-(v1.2.0)EndUserLicenseAgreement(EULA)-_Toc529728678) [3. License Scope](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/v1.2.0/end-user-license-agreement-eula.md#id-(v1.2.0)EndUserLicenseAgreement(EULA)-_Toc529728679) [4. Terms of Use](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/v1.2.0/end-user-license-agreement-eula.md#id-(v1.2.0)EndUserLicenseAgreement(EULA)-_Toc529728680) [5. Intellectual Property](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/v1.2.0/end-user-license-agreement-eula.md#id-(v1.2.0)EndUserLicenseAgreement(EULA)-_Toc529728681) [6. Consideration](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/v1.2.0/end-user-license-agreement-eula.md#id-(v1.2.0)EndUserLicenseAgreement(EULA)-_Toc529728682) [7. Personal Data](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/v1.2.0/end-user-license-agreement-eula.md#id-(v1.2.0)EndUserLicenseAgreement(EULA)-_Toc529728683) [8. Update Versions](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/v1.2.0/end-user-license-agreement-eula.md#id-(v1.2.0)EndUserLicenseAgreement(EULA)-_Toc529728684) [9. Support](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/v1.2.0/end-user-license-agreement-eula.md#id-(v1.2.0)EndUserLicenseAgreement(EULA)-_Toc529728685) [10. Guarantees and Liability](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/v1.2.0/end-user-license-agreement-eula.md#id-(v1.2.0)EndUserLicenseAgreement(EULA)-_Toc529728686) [11. Publicity](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/v1.2.0/end-user-license-agreement-eula.md#id-(v1.2.0)EndUserLicenseAgreement(EULA)-_Toc529728687) [12. Confidentiality](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/v1.2.0/end-user-license-agreement-eula.md#id-(v1.2.0)EndUserLicenseAgreement(EULA)-_Toc529728688) [13. Term of the Agreement](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/v1.2.0/end-user-license-agreement-eula.md#id-(v1.2.0)EndUserLicenseAgreement(EULA)-_Toc529728689) [14. Changes to Agreement](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/v1.2.0/end-user-license-agreement-eula.md#id-(v1.2.0)EndUserLicenseAgreement(EULA)-_Toc529728690) [15. Miscellaneous Terms](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/v1.2.0/end-user-license-agreement-eula.md#id-(v1.2.0)EndUserLicenseAgreement(EULA)-_Toc529728691) [16. Data Processing Regulations](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/v1.2.0/end-user-license-agreement-eula.md#id-(v1.2.0)EndUserLicenseAgreement(EULA)-_Toc529728692) [Data Processing Addendum](https://mgm-atlassian-apps.mgm-tp.com/link-workflow-graphic-for-jira/v1.2.0/end-user-license-agreement-eula.md#id-(v1.2.0)EndUserLicenseAgreement(EULA)-_Toc529728693) ## 1. Definitions This End User License Agreement (hereinafter referred to as: "the Agreement") is between YOU, meaning your organization, represented by an authorized representative (hereinafter referred to as "User") and mgm technology partners GmbH, a private limited liability company having its principle place of business in Munich, Germany, registered with the Munich Commerce Register Court under number HRB 161298 (hereinafter referred to as "mgm"). The mgm add-ons, plugins or any other mgm products (hereinafter collectively referred to as: "Artifacts") are made available online on + and certain third party websites, hereinafter referred to as "Website". mgm may modify this Agreement from time to time, subject to the terms set out in this Agreement. ### 2. License Version This license is dated October 31^st^, 2018 and replaces all earlier versions. ### 3. License Scope mgm hereby grants the User a limited right to use the Artifacts. This license is non-exclusive and non-transferable. Only the authorized number of users may actually use the Artifacts. Additional license keys may be purchased through the Website. It is expressly forbidden to * decompile the Artifacts or to reverse engineer the source code of the Artifacts, except to the extent permitted by mandatory law or applicable open source license, * provide copies of the Artifacts to third parties, * sublicense the Artifacts or otherwise make available the Artifacts to third parties, including by rental, Software-as-a-Service models or otherwise, * modify the Artifacts, except to the extent permitted by mandatory law, * remove any indication of mgm as copyright holder of the Artifacts or to remove or render illegible any part thereof. ### 4. Terms of Use You are solely responsible for installation and usage of the Artifacts. The online available documentation will provide recommended requirements for the hardware and software environment. It is not permitted to use the Artifacts for any purpose that violates German or other applicable law or regulation. In particular it is not permitted to use the Artifacts in a manner that causes a nuisance or hindrance for other users. If in the opinion of mgm the continued functioning of the computer systems or network of mgm or third parties is under threat of being damaged or jeopardized, for example through excessive transmission of e-mail or other data, leaks of personal data or virus activity, mgm may take all steps it finds reasonably necessary to end or avert such damage or jeopardy. mgm is at all times entitled to file a criminal complaint for any offenses committed through or by using the Artifacts. In addition, mgm is entitled to supply User's name, address, IP-address and other identifying data to a third party alleging that User violates its rights or these terms and conditions, provided the validity of the complaint is clear, no other way of obtaining this information exists and the third party has an evident interest in obtaining this information. ### 5. Intellectual Property All right, title and interest to the Artifacts, the accompanying documentation and all modifications and extensions thereto belong, rest and remain with mgm. The User only has the rights and permissions explicitly granted to him by this Agreement or granted in writing otherwise. User may not use, copy, distribute or publish the Artifacts in any other manner. The Artifacts may be comprised of third-party open source software. The respective third-party right holders grant you the rights indicated in the applicable open source licenses. These licenses can be found in the documentation accompanying the Artifacts. This Agreement does not apply to this open source software, and nothing in this Agreement shall be construed as a limitation of any right granted to you under an open source license. ### 6. Consideration Unless agreed upon differently through a written contract between the User and mgm, a license for the Artifacts can only be obtained through the Website. Prices and payment details are specified on the Website. Certain Artifacts are available for a limited period at no charge. After this period a full license with a well-defined period of validity is due. This will be indicated on the Website or in the Artifacts. Prices are shown in the currency mentioned on the Website, and are shown exclusive of VAT, import duties and other government imposed taxes, duties and levies. Shortly after payment, the User may download and install the Artifacts. Prior to this, verification of the User may be required in order to ensure User is an authorized User. The Artifacts and/or the Website will inform the User of any procedures and additional conditions. ### 7. Personal Data During the installation and/or payment procedure, mgm and/or any third party processes certain of the personal data of the User. In addition to the data requested in the order form, the IP-address from which the registration is undertaken is recorded, as well as information regarding the used software. These personal data are only used for the execution of the Agreement and related purposes such as the making of related offers or notifications of available updates. For further information see the . Other terms and conditions regarding processing of Personal Data while using the Artifacts are put forward in Appendix A: the Data Processing Addendum. ### 8. Update Versions mgm may periodically release updates to or newer versions of the Artifacts that may address bugs or improve the functioning of the Artifacts. To learn about the latest versions, consult the Website regularly. No liability is accepted for any damage caused by bugs addressed in an update not installed by the User. ### 9. Support mgm shall provide the User with a reasonable level of support through the Website and e-mail or other communication channels announced to the User. mgm does not guarantee that all requests for support or bug reports are taken into consideration. ### 10. Guarantees and Liability mgm guarantees that the Artifacts substantially operate as described in the documentation; that the Artifacts contain no viruses, backdoors or malicious routines. mgm will use its best efforts to investigate any reported bugs as soon as is practical and to repair such bug or create a workaround (but may delay repairing bugs with limited impact until the next planned version), mgm grants no additional guarantees and/or warranties. In particular, mgm makes no representation or warranties, either expressed or implied, that any services rendered or any design or process which is the result of a particular use of the Artifacts, will not infringe any patent, copyright, or proprietary right of any kind of any third party, and mgm will have no liability whatsoever for any claim or suit against the User by any other party for such infringement. Except in case of intentional misconduct or gross negligence, the liability of mgm for damages in connection with the Artifacts or the violation of a warranty granted above is limited to an amount equal paid by User under the Agreement in the 6 (six) months prior to the damage-causing incident occurred. mgm in no event is liable for indirect damages, consequential damages, lost profits, missed savings or damages through business interruption. The total compensation for damages will in no case exceed the amount of EUR 500 (five hundred Euros). The obligation for mgm to pay compensation will only arise if the User sends written notice to mgm of this damage within fourteen (14) days after the damage occurring. ### 11. Publicity User hereby authorizes mgm to identify User as a customer of mgm within its promotional materials. Should User wish to object to such use, it may do so at any time by submitting an e-mail to [atlassian-info@mgm-tp.com](mailto:atlassian-info@mgm-tp.com). Please note that it may take up to 30 days to process this request. ### 12. Confidentiality Both parties shall refrain from disclosing or using for any other purpose than within the scope of this Agreement, any trade secrets and other information of the other party that has been designated as confidential or the confidential nature of which is known or can reasonably be deemed to be known by the other party. Both parties accept the duty to observe strict secrecy towards third parties with respect to all matters which have been arranged in this Agreement. In addition, the parties accept the duty to observe strict secrecy with respect to all information regarding the business, activities and organization of the other party, except in as far as such information was already part of the public domain without any involvement of the other Party. ### 13. Term of the Agreement This Agreement is entered into for the (subscription) period stated on the Website or as stated elsewhere (hereinafter: "the Contract Period"). If the Contract Period is not stipulated, it shall be deemed to have been entered into for a Contract Period of 12 (twelve) months. Unless agreed to the contrary, this Agreement, in the absence of termination in writing reaching mgm at least 2 (two) months before the end of the Contract Period, shall always be tacitly extended by the same Contract Period. mgm and/or third party will usually send User a notice for the extension of licenses and payments that may be due in that regard. This Agreement terminates automatically and immediately in case the User enters into bankruptcy, or the User applies for suspension of payments, or the assets of the User are seized, or in case the User enters into liquidation, legal dissolution or winding-up. After termination of the Agreement, regardless of the reason, User must cease all use of the Artifacts. In addition User must remove all copies (including backup copies) of the Artifacts from all computer systems under control of User. ### 14. Changes to Agreement mgm may update or modify this Agreement from time to time, including any referenced policies and other documents. If a revision meaningfully reduces User's rights, mgm will use reasonable efforts to notify User (by, for example, sending an e-mail to the billing or technical contact you designate in the applicable order, posting on our blog, through your Atlassian account, or in the Product itself). If mgm modifies the Agreement during license term and/or subscription term, the modified version will be effective upon your next renewal of a license term, support or maintenance term, and/or subscription term, whichever applies. In this case, if User objects to the updated Agreement, as your exclusive remedy, you may choose not to renew, including cancelling any terms set to auto-renew. With respect to Artifacts available for free, accepting the updated Agreement is required for you to continue using those Artifacts. You may be required to click through the updated Agreement to show your acceptance. If you do not agree to the updated Agreement after it becomes effective, you will no longer have a right to such Artifacts. For the avoidance of doubt, any order is subject to the version of the Agreement in effect at the time of the order. ### 15. Miscellaneous Terms German law applies to this Agreement exclusively. Unless dictated otherwise by mandatory law, all disputes arising in connection with this Agreement shall be brought before the competent German court for the principal place of business of mgm which is in Munich. A finding that any particular provision of this Agreement is legally void or unenforceable shall not affect the validity of the entire Agreement. In such a case the parties shall determine a replacement provision that is legally valid and approximates the intent of the relevant provision as much as possible. mgm may assign its rights and obligations under this Agreement to a third party that acquires the relevant business or the copyrights to the Artifacts from her. ### 16. Data Processing Regulations It is possible that by using the Artifacts, the End User processes personal data and therefore, that mgm processes that personal data on behalf of the End User, especially in cases of analyzing problems via log files or alike. In that case, the following articles apply, complementary to the Agreement and the Privacy Policy. The applicability of any data processing agreement or addendum preceding this data processing addendum or issued by the End User is strictly rejected. Appendix A: ### Data Processing Addendum #### Introduction and definitions 1. The word "End User" as applied in this Data processing addendum means your organization, represented by an authorized representative. The word "End Users" as applied in this data processing addendum means any individual in or represented by your organization that uses the Artifacts, either as an administrator or a user. 2. Definitions that are used in this data processing addendum derive their meaning from their definitions as meant in the EU General Data Protection Regulation (GDPR). 3. This Data Processing Addendum qualifies as a data processing agreement as described in Article 28 GDPR. 4. If the End User processes personal data by using the Artifacts, mgm processes such personal data on behalf of the End User. Consequently, the End User and mgm agree that the End User is regarded as the data controller and mgm is regarded as the data processor. Alternatively, if the End User is processing personal data on behalf of a third party, the End User is regarded as the data processor and mgm is regarded as the data sub-processor. ##### Description of Data Processing 1. mgm commits to process personal data on behalf of the End User, under the conditions of the Agreement, which reflect the written instructions by the End User for the processing of personal data. mgm will solely process the personal data in the context of the Agreement and the Privacy Policy, their duration and purpose, and other purposes that can reasonably be associated with their purpose or purposes that are to be defined under future consent. 2. mgm will not process the personal data for purposes different from the purposes as set forward in the Agreement and the Privacy Policy. The End User will inform mgm of purposes for the processing of personal data that are not yet mentioned in the Agreement. 3. mgm has no saying in the purpose and means of the processing of the personal data. Additionally, mgm has no saying in the nature of the personal data that is processed. All personal data processed in connection with the Artifacts shall deemed to have been processed at the instructions of the End User. 4. mgm will not make independent decisions about the data gathering and use of the personal data, the provision to third parties, the duration and the storage of the personal data. 5. The personal data are related to the following data subject categories: 1. People who use the Artifacts (the End Users); and/or 2. People whose personal data is captured or processed in the Artifacts by End Users; and/or 3. People whose data is transmitted via the Artifacts by End Users; and/or 4. Other possible data subject categories whose personal data is processed using the Artifacts. ##### Non-disclosure and Confidentiality 1. mgm is bound to non-disclosure against third parties for all personal data that mgm processes on behalf of the End User, following from this Data Processing Addendum. mgm will not use this data for any other purpose than for which mgm received the data from the End User, except if the data is altered (encrypted or a anonymized) in such a way that it is no longer traceable to an individual data subject. 2. The non-disclosure as meant in DP-3 section 1 is not applicable: 1. to the extent that the End User has provided mgm the permission to provide the data to third parties; or 2. when the provision of the data to third parties is logically necessary for the use or proper functioning of the Artifacts or the execution of this data processing addendum; or 3. if a legal requirement or court order exists to provide the data to third parties; or 4. in regard of third parties to which personal data are provided in their role as sub-processor, taking into account the conditions defined in ‎DP-5. ##### Security and Technical and Organizational Measures 1. With regard to the processing of personal data, mgm will strive to take adequate technical and organizational measures, in particular to safeguard against the destruction, loss, mutation or unauthorized provision or unauthorized access to transferred, stored or otherwise processed personal data. 2. The technical and organizational measures that mgm takes follow from the most recent version of their information security policy can be provided by mgm upon justifiable request. 3. In case, in mgm's opinion, this is necessary to offer a continued adequate level of security, mgm is allowed to make changes to the security measures. 4. mgm does not guarantee that their security is effective under all conditions. mgm will strive to maintain a reasonable level of security, taking into account the state of technology, implementation costs of the security measures, the nature, extent and context of the processing of personal data, the purposes and the intended use of the Artifacts, the data processing risks and the risks for the rights and freedoms of data subject, which they may have expected considering the intended use of the Artifacts and which are divergent for their probability and impact. 5. The End User asserts that the security measures as meant or referred to in ‎DP-4, considering the factors as described herein, provide an adequate level of security that is in accordance with the risks of the processing of personal data processed by or provided by the End User. 6. The End User will only provide personal data for processing to mgm if the End User has ensured themselves that the required security measures are taken. The responsibility for the compliance of the measures as agreed between the End User and mgm resides with the End User. ##### Sub-Processors 1. The End User provides mgm the general permission to work with third parties (sub-processors) for the processing of personal data. mgm always work with their associated companies in the European Union and in countries outside of the European Union, while taking into account relevant laws and regulations. 2. Upon request by the End User and within a reasonable time frame, mgm will inform the End User about the relevant third parties that mgm works with, regarding the processing of the personal data as meant in this data Processing Addendum. 3. mgm has the right to add or replace third parties (changes). If mgm intends to add or replace a third party, mgm will inform the End User accordingly, allowing the End User to object. If the End User wishes to object, the End User must submit their objection in written form, within two weeks and supported by sound argumentation. If the End User does not object within these conditions, the End User is regarded to accept the intended change. 4. If the End User objects within the conditions as stated above in ‎DP-5 section ‎2, mgm and the End User will consult each other and strive to achieve a reasonable solution. If both parties cannot achieve a satisfactory agreement about the intended change as meant above in ‎DP-5 section ‎2, mgm is entitled to work with the respective added or replaced third party. Respectively, the End User is entitled to terminate their subscription to the Artifacts per the date that the new sub-processor is activated. 5. At all times, mgm ensures that the third parties as meant in this article will take on the same obligations as agreed between the End User and mgm in writing and ensures the compliance by these third parties of these obligations. ##### Transfer of Personal Data 1. mgm processes personal data in countries of the European Union. Additionally, the End User permits mgm to process personal data in countries outside of the European Union, while taking into account relevant laws and regulations. 2. Upon request and within a reasonable time frame, mgm will inform the End User in which countries mgm processes the personal data. ##### Data Subject Rights and Requests 1. If a data subject submits a request about their personal data to mgm in order to exercise their data subject rights, mgm will forward the request to the End User and inform the data subject accordingly. The responsibility for processing the request and performing data subject rights lies with the End User, who will process the request and perform the data subject rights independently from mgm. 2. mgm will provide assistance to the End User for processing a request by a data subject and performing their data subject rights, should this occur to be necessary. mgm may charge the End User for reasonable expenses that are made or to be made while providing such assistance, which will be reimbursed by the End User. ##### Obligations and Support 1. mgm will commit to compliance with the conditions that, based on the GDPR, are bound to the processing of personal data by mgm in their specific role, regarding the processing of personal data as meant in ‎DP-2 of this data processing addendum. 2. mgm will process personal data and other forms of data that are made available to mgm by the End User based on written instructions by the End User. 3. Upon request and within a reasonable time frame, mgm will inform the End User about the (technical and organizational) measures taken by mgm to comply with their obligations as meant under this data processing addendum. 4. The obligations as meant in this data processing addendum are also applicable to parties that process personal data under mgm's authority. 5. If, in mgm's opinion, an instruction given by the End User is conflicting with relevant laws and regulations, mgm will inform the End User. 6. At the request of the End User, mgm will, within a reasonable time frame, provide the End User with the necessary cooperation to meet their compliance with the obligations that follow from the GDPR. This includes, among others, their obligations with regard to data security, reporting personal data breaches and performing data protection impact assessments. mgm will charge the End User for reasonable expenses that are made or to be made while providing such cooperation, which will be reimbursed by the End User. ##### Personal Data Breaches 1. A personal data breach is defined as a violation of security that accidentally or unlawfully leads to the destruction, loss, mutation or the unauthorized provision or unauthorized access to transmitted, stored or otherwise processed personal data. 2. If a personal data breach occurs, mgm will inform the End User to the best of their abilities, abiding by applicable laws and regulations. The End User will then judge if they need to inform the supervisory authorities and/or data subjects. mgm strives to ensure that the information is complete, correct and accurate to the best of their abilities. 3. mgm will cooperate with informing the relevant authorities and, if required, the data subjects, should this be required by any law or regulation. The responsibility for informing the relevant authorities and the data subjects resides with the End User. 4. If a personal data breach has occurred, mgm will provide the following information to the End User: 1. The fact that a personal data breach has occurred 2. the (supposed) cause of the breach 3. the (then known or expected) effects 4. the (proposed) resolution 5. the taken measures 6. the contact details for the follow-up of the issue 7. an overview of the informed parties (e.g.: the data subjects) ##### Destruction or Return of Personal Data 1. After termination of this data processing addendum, mgm will destroy the personal data it has received from the End User without delay, except if mgm and the End User agree that mgm will return the personal data to the End User or retain the personal data for an agreed period, or if mgm is required by law to retain the personal data. 2. mgm may charge the End User for reasonable expenses that are made or to be made for the destruction or the return of the personal data to the End User, which will be reimbursed by the End User. ##### Audits 1. For the verification of compliance of all items from this data processing addendum, the End User has the right to issue audits by a competent and independent party. 2. This competent and independent party is bound to non-disclosure. 3. An audit will only be conducted after the End User has requested the available similar audit reports from mgm, has judged the reports and provides sound argumentation why an audit, initiated by the End User, is still justifiable. Such an audit will only be justifiable when the similar audit reports that are available from mgm provide no or insufficient proof about the compliance of this data processing addendum by mgm. If an audit, initiated by the End User, is justified, it will only be conducted at least 30 days after prior announcement by the End User, with a maximum of once per year. 4. mgm will cooperate with the audit and will provide all information that is reasonably relevant for the audit, including supportive information such as system logs and access time to relevant employees, as timely as possible and within a reasonable time frame (within two weeks or sooner in case of an urgent interest). 5. In mutual consultation, the End User and mgm will judge the findings that may result from the audit. As a result of this process, measures may be implemented by either mgm, the End User or both parties. 6. Reasonable expenses made or to be made by mgm in this process will be reimbursed by the End User. The expenses for the hired competent and independent party are always the responsibility of the End User and will be met by them. ##### Distribution of Responsibilities 1. Both mgm and the End User commit to compliance with applicable laws and regulations. mgm performs the processing of personal data under the scope of the Agreement and the Privacy Policy in a (semi)automated environment. 2. mgm is only responsible for the processing of personal data as meant in this data processing addendum, abiding by the instructions of the End User and under the explicit (final) responsibility of the End User. 3. mgm is not responsible for all other processing of personal data, including but not limited to the collection of personal data by the End User, processing of personal data for purposes that the End User failed to report to mgm, processing by third parties and processing for other purposes. For such processing of personal data, the End User has the exclusive responsibility. At all times, the End User guarantees the legality of their processing of personal data and the adequacy of the security of their systems and infrastructure. 4. The responsibility for judging whether mgm offers adequate safeguards regarding the implementation of technical and organizational measures in order for the processing of personal data to be compliant with the demands from the GDPR and/or other applicable laws and regulations and whether the protection of the rights of the data subjects is adequately safeguarded, lies with the End User. 5. At all times, the End User guarantees that the content, use and instructions for the processing of personal data as meant in this data processing addendum is not unlawful and does not infringe any rights of third parties. 6. Notwithstanding other rights of mgm, the End User safeguards mgm from all legal claims by third parties, from any source, if the legal claim relates to the processing of personal data. Additionally, the End User safeguards mgm from potential damages and fines, imposed by competent supervisory authorities, for which the End User is accountable and/or if the End User violates this data processing addendum, the GDPR or any other applicable laws and regulations. ##### Duration and Termination 1. The duration of this data processing addendum is identical to the duration as defined in the Agreement or contract that is agreed upon between mgm and the End User. If there is no duration defined in any of these documents, the duration of this data processing addendum is identical to the duration of the collaboration between the End User and mgm. 2. This data processing addendum cannot be terminated intermediately. 3. ‎‎DP-3 (Non-disclosure and Confidentiality) will survive the termination of the data processing addendum. 4. mgm and the End User may only change this data processing addendum with mutual consent. [Next Page](https://mgm-atlassian-apps.mgm-tp.com/llms-full.txt/1)