Hyper for Jira

What Hyper reads

Hyper keeps a searchable copy of every issue that you can open, in all your Jira sites, from all time. For each issue, it copies every field, such as the title, status, assignee, description, and comments, and the names of attached files, but not what is inside the files. It also copies each project with its issue types, the names and emails of the people in each site when Jira shows them, and boards and sprints if you use Jira Software. It does not copy issue history, archived projects, filters, or dashboards. Hyper checks for changes about every 10 minutes. A deleted issue can stay in Hyper for up to a month. When you ask, Hyper can also read issue history, work logs, attached files, filters, dashboards, users, groups, and site settings.

What Hyper can do

Create, change, move, assign, and delete issues, one at a time or many at once. Add, change, and delete comments, work logs, links, and attached files. Watch issues and email people about an issue. Create, change, archive, and delete projects, versions, and components. Manage filters and dashboards. If you are a Jira admin, Hyper can also change workflows, fields, screens, permissions, users, and groups. Hyper can move issues into sprints, but it cannot change boards or create, start, or close sprints. Hyper asks you before each action, unless you chose to always allow that kind of action. It always asks before it uploads a file.

Before you connect

Hyper can read every issue that you can open, in every site, including private projects. Changes show your name, and Jira emails the people who watch an issue when it changes. A deleted issue is gone for good, with its comments and attached files. Archiving issues needs a Jira Premium or Enterprise plan. Your Atlassian admin can block apps like Hyper. Anyone who can write an issue or comment can add text that hides instructions that try to trick an assistant, so check each change before you approve it.