Support

How to reach me

Key Result Relay is made and supported by me, Christian Ortiz, publishing as Christian Ortiz Studio. Email support@christianortiz.studio and the message comes straight to me. There’s no ticket queue to get lost in.

Before you write, the documentation may already have the answer, especially its FAQ and troubleshooting sections. In the app, Help (the question mark) has the same how-tos and FAQ, and Show tour again. Jira admins can run the setup check, which names most problems and their fix.

When you’ll hear back

I reply to every message within two business days (Monday to Friday, 5 pm to 9 pm US Pacific Time), and usually sooner. If messages are going to the wrong channel, put Urgent in the subject line and I’ll treat it as my first priority.

Report a bug or a missed message

Email me with as much of this as you can:

• Your Jira site address (for example your-site.atlassian.net).
• The result of Run checks on Setup, with any red or yellow row word for word.
• For a key result that looks wrong: its JQL and rule, the numbers on its page, and what you expected.
• For a missed message: the Objective, the routing rule (channel, events, threshold, hour) and roughly when you expected it. Recent delivery failures on Setup shows what Slack or Teams answered.
• What you did, what you expected, and what happened instead, with a screenshot if you can.

The app sends me nothing about your site, so your email is how I find out. I’ll confirm I can reproduce it, tell you what I’m doing about it, and let you know when a fix is released.

Report a security issue

If you’ve found a security problem, email me with Security in the subject line and include how to reproduce it. Please don’t post it publicly until it’s fixed. I acknowledge security reports within two business days.

Request a feature

I’d like to hear it. Tell me how your team runs OKRs and where the app gets in the way; the most useful requests describe the job, not just the button. I read every one, and I’ll tell you honestly whether it’s likely to be built.

Delete your data

• An Objective, key result or check-in: delete it in the app. Deleting an Objective deletes its key results, their check-ins and change logs, and its routing rules. Deleting a key result deletes its check-ins and change log.
• A channel: in Chat Channels, ••• → Delete. The webhook URL secret is deleted with it.
• Delivery logs are deleted automatically after 30 days; each key result keeps its latest 500 changes.
• Closed accounts are handled automatically: Atlassian tells the app when an account is closed, and the app replaces that person’s account ID with an anonymous marker within a week.
• Uninstall the app to remove all of its data from your site, after Atlassian’s 28-day retention for Forge storage.
• Ask me: email me with Data deletion in the subject and your site address. I’ll help, reply within two business days, and confirm what was removed.

Messages already posted to Slack or Teams are in those services and are deleted there, under their own controls.

The privacy policy lists everything the app keeps and for how long.

Licenses, billing and refunds

Purchases, renewals, invoices and refunds go through Atlassian, under the Atlassian Marketplace Terms of Use. For those, contact Atlassian, or a site admin can manage the app under Manage apps. I’m still happy to help if you’re not sure where to start.