Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Next »

General Questions

 How actively is Custom Charts being developed?

Very actively! We have a whole development team dedicated to building and supporting Custom Charts.

You can follow our latest updates on Twitter.

 Where is Custom Charts public feature roadmap?

You can follow all our recent releases and upcoming features on our actively maintained public feature roadmap.

 I need help, who can I contact?

If you'd like to ask us a question about Custom Charts please raise a ticket in our support portal or send an email to support@oldstreetsolutions.com

Please let us know if you find a bug with our apps so we can fix them as soon as possible!

Our support team is here to help (smile)

 Which Jira fields are supported by Custom Charts?

Chart By Options - Supported Fields

Jira Service Desk Fields

The following Jira Service Desk fields are supported in Custom Charts

JSD FieldJira CloudJira Server & Data CenterNotes
Request Type(tick)(tick)Supported
Request Channel Type(tick)(tick)Supported

Request Language

(tick)(tick)Supported
Satisfaction Rating(tick)(tick)Supported
Organizations(tick)(tick)Supported
Approvers(tick)(tick)Supported
SLAs

(tick)

Using Custom JQL

Example 🔗

(tick)

Using Custom JQL

Example 🔗

Supported
‌‌ 




System Fields

The following Jira system fields are supported in Custom Charts

System FieldJira CloudJira Server & Data CenterNotes
Summary(tick)(tick)Supported
Assignee(tick)(tick)Supported
Creator(tick)(tick)Supported
Epic Link(tick)(tick)Supported
Epic Status(tick)(tick)Supported
Issue Type(tick)(tick)Supported
Priority(tick)(tick)Supported
Project(tick)(tick)Supported
Reporter(tick)(tick)Supported
Resolution(tick)(tick)Supported
Reviewed(tick)(tick)Supported
Status(tick)(tick)Supported
Status Category(tick)(tick)Supported
Labels(tick)(tick)Supported
Component/s(tick)(tick)Supported
Affects Version/s(tick)(tick)Supported
Fix Version/s(tick)(tick)Supported
Labels(tick)(tick)Supported
Sprint(tick)(tick)Supported
Story Points(tick)(tick)Supported
Epic Name(tick)(tick)Supported
Environment(tick)(tick)Supported
Security Level(tick)(tick)Supported
Created Date(tick)(tick)Supported
Updated Date(tick)(tick)Supported
Due Date(tick)(tick)Supported
Time Tracking(warning)(warning)Coming soon!
Work logged(warning)(warning)Coming soon!
Attachment(error)(error)Not currently supported
Description(error)(error)Not currently supported
Development(error)(error)Not currently supported
Epic Color(error)(error)Not currently supported
Linked Issues(error)(error)Not currently supported
Rank(error)(error)Not currently supported





Custom Field Types

The following custom field types are supported in Custom Charts

Custom Field TypeJira CloudJira Server & Data CenterNotes
Select List (single choice)(tick)(tick)Supported
Select List (multiple choices)(tick)(tick)Supported
Radio Buttons(tick)(tick)Supported
Check Boxes(tick)(tick)Supported
User Picker (single user)(tick)(tick)Supported
User Picker (multiple users)(tick)(tick)Supported
Labels(tick)(tick)Supported
Number(tick)(tick)Supported
Project Picker (single project)(tick)(tick)Supported
Version Picker (single version)(tick)(tick)Supported
Version Picker (multiple versions)(tick)(tick)Supported
Text Field (read only)(tick)(tick)Supported
Text Field (single line)(tick)(tick)Supported
Text Field (multi-line)(tick)(tick)Supported
Select List (cascading)(tick)(tick)Supported
Date fields(tick)(tick)Supported
Date and time fields(tick)(tick)Supported





Custom Fields - 3rd party apps

Many 3rd party apps are supported by Custom Charts.

If you find a custom field that isn't supported, please suggest a new custom field.








 How can I export my charts?

All charts can be exported directly as PNG, PFD and CSV

https://ossapps.atlassian.net/browse/TRACC-15

Confluence

On Confluence Server & Data Center, exporting pages to PDF or Word will export all charts on the page.

On Confluence Cloud, exporting to PDF and Word is slightly complicated because of a security consideration when saving data. Other apps on Confluence Cloud will save a .png of their app (e.g. a diagram) to the page which is then used for the PDF export. This is fine for a diagram when all users viewing the page see the same data, but Custom Jira Charts loads every page as the user who is currently logged in. This means that each user would potentially see a slightly different chart. While this isn't an insurmountable problem, it's not one that we have found a solution for quite yet but is on our public roadmap.

https://ossapps.atlassian.net/browse/TRACC-41

 How do I create a chart using a cascading select list?

Currently, it is only possible to directly drive a chart with dynamic values from the first option in a cascading field. However, we do have a feature called Custom JQL that should allow you to build the charts you need. Here is an example that uses the JQL "Cascade Test" = A AND "Cascade Test" = 1 which will find only issues where the value of the cascading field is both A and 1.

 In future, my company plans to migrate from Server / Data Center to the Atlassian Cloud. Can Custom Charts be migrated to Cloud and are the features different on Cloud?

Custom Charts has identical features on Cloud, Server and Data Center.

Migrating from Confluence Server & Data Center to Confluence Cloud works seamlessly. Simply export a page, space or entire instance and import to your Confluence Cloud site. When you install the Cloud version of the Custom Jira Charts for Confluence app your charts will be configured exactly as before.

Note: Charts with User Impersonation enabled will be imported with User Impersonation turned off. This is to ensure that Custom Charts are secure by default and, therefore, charts must be edited and re-assigned an Impersonation User after importing.

Migrating dashboards with custom gadgets from Jira Server & Data Center to Jira Cloud isn’t currently supported by Atlassian. This feature is a top priority for our development team and we are actively working with Atlassian on this functionality.

  • No labels