Support - Jev for Jira

01

Get help

Contact We The Folks for help with Jev for Jira, installation, automation configuration, unexpected results, or data requests. Include “Jev for Jira” in the subject and a short description of what you need.

Support is provided by email. This page does not promise a response time or round-the-clock coverage.

Email [email protected]

02

Start with these checks

Open Jev for Jira and select the affected project. Classification automations and Activity log show configuration and recorded results. The next tab, Data processing, contains site-wide processing settings, independently of the selected project.

Access

You need project administration access for the selected project, or Jira site administration access. Activity also requires permission to view the referenced issue.

Site consent

Open Data processing to review Manage site processing. A Jira site administrator must authorize external processing before classification can run. Only a site administrator can grant or withdraw that consent; project administrators see an explanation of the required permission.

Service message

The page checks model availability automatically. Credential, credit, or provider access problems need We The Folks to investigate; customers do not manage the OpenRouter key.

Automation state

Check that the rule is enabled and the event matches its trigger. Saving enables the rule but does not backfill existing issues.

Future items

When Apply only for future items is enabled, issues created before its saved cutoff are excluded from automatic execution. Updating an older issue does not make it eligible.

03

Check a classification safely

Save configuration changes, then use Test beside the saved automation. Enter an issue key you are authorized to access. The result shows outcome probabilities and planned actions; it does not edit the issue or enable a disabled rule.

A test still sends the configured prompt and referenced Jira data to OpenRouter and TypeSafe. Use a suitable test issue and avoid sensitive content that your organisation has not authorized for external processing.

If a request is too large, reduce the Jira values or repeated variables used in the prompt and outcome descriptions. The application rejects requests above its 30,000-byte expanded request budget instead of silently truncating them.

04

Understand activity results

Activity entries are available for up to 14 days. Capture the relevant time and safe error message while they are visible.

Waiting for service

A captured automatic event is waiting for provider recovery. A background check runs every five minutes. Retry now requests an immediate recovery check for pending classifications in the selected project; it does not bypass consent or permissions.

Recovery cancelled

Recovery rechecks current issue data, permissions, consent, and the original rule revision. Changing or disabling the rule can cancel waiting work. Events remain recoverable for at most 14 days from their original queue time.

Skipped

An action may already match the issue’s current value. Read its reason before assuming the automation failed.

Failed action

Review the safe failure message, current Jira permissions, configured field values, and any move destination requirements. A successful classification does not mean every Jira action succeeded.

Needs review

A Jira write could not be confirmed. Inspect the actual issue and its history before making another change. The app does not blindly replay an uncertain write.

05

What to include in a support request

Describe the expected result, what happened, steps to reproduce it, the date and time with timezone, and whether this was a Test or an automatic run. Include the visible status and sanitized error text.

Share your Jira site address and issue or project identifiers only when your organisation permits it and they are needed to identify the problem. Crop or redact screenshots, including prompts, rule names, and outcome labels that may contain personal data.

Do not email API keys, passwords, session cookies, authentication headers, full Jira issue exports, or unredacted sensitive content. A small synthetic example is usually a better starting point. We do not need your Jira credentials.

06

Data and security questions

For a suspected security problem, start with a brief description without secrets or customer issue content. Contact us to agree how to provide any sensitive reproduction material.

For installation-specific deletion or data-processing questions, identify the installation and the scope of the request. Uninstalling the app does not guarantee immediate physical deletion from Atlassian or external provider systems.

Security controls and limitations

Data processing and retention

Contact

Jev for Jira support: [email protected].

Provided by We The Folks sp. z o.o. Please send only the information needed to investigate.