TELCOMA Global  /  Customers & Organizations Export  /  Support

Supported by the people who built it.

One address, one promise: a reply within one business day, and within four business hours if the app has stopped working on your site. The app is free; the support is the same.

What to include

Four things, and we can usually answer from them alone.

  • Your Jira site URL, for example yourcompany.atlassian.net
  • The service project, the scan (when it finished) and the customer or organization you were looking at
  • What you expected and what you saw, for example a count that differs from a Jira search
  • The message the app showed, word for word

We never need your password, API tokens, or access to your site. If anyone claiming to represent us asks for those, it isn't us.

Support and security reports
[email protected]
Response time
Within one business day (Mon–Fri, 09:00–18:00 IST)
If the app has stopped working
Within four business hours
Documentation
Customers & Organizations Export documentation

Please do not post security reports publicly. Email them.

Known limits

Known limits

Every one of these follows from what Jira Service Management does and doesn't expose to apps, or from the app being read-only on purpose.

Open means no resolution

Resolved means the Resolution field is set, as in Jira. Requests in a done status with no resolution count as open, and the page says how many there are.

Counted for the reporter

A request counts for the person shown as its reporter, and for each organization it is shared with. Not for the members of that organization one by one.

Customer list only

In a project that lets anyone raise requests, people never added as customers are not listed. Their requests, and agents' requests, are counted in a note on the page.

Requests the app can browse

Requests hidden from the app, for example by an issue security level, are not counted.

Hidden emails

Emails are empty for people whose profile settings don't share them with apps. The page and the export say why.

Some portal-only names

On a big project, some names of portal-only customers can stay empty. The account ID is shown instead, with the reason.

A snapshot

Each scan shows the project as it was when the scan ran. Scan again after you change customers or organizations.

It shows, it doesn't change

To add or remove customers and organizations, use Jira Service Management's own settings.

Service status

The app runs entirely on Atlassian Forge. If Jira Cloud or Forge is degraded, the app is affected. See status.atlassian.com.

Feature requests

Tell us what you still can't find out about your customers and organizations. Requests that come with the reason behind them get built first.

Privacy

What the app reads, stores and never does, in plain terms: the privacy policy.