HeyBobTurn the conversation into tracked work.
Connect Jira and Bob searches issues, files new ones, updates them, comments and moves them along, asking before anything changes. In the HeyBob app on Mac, Windows and Linux, or in Slack.
- Jira’s permissions still apply
- Asks before every change
- A receipt on every job
What Bob can do in Jira.
Jira lets every company shape its projects, fields and workflows differently, which is why hand-built automations keep breaking. Bob reads the project first and fits the request to it.
Search and report
Find issues, read them and pull together project status.
File and edit
Create issues, change fields and add comments.
Move work along
Move an issue to its next status, like In review or Done.
Six things to hand him.
Search first, then file. That is how the duplicates stop.
“Read this support thread and search Jira for related checkout incidents. If nothing matches, draft a Severity 2 issue in PAY with the evidence and customer impact.”
He only files a new ticket when there is no match.
“Every weekday at 8:30, find open blockers in Mobile and API, group them by owner, and post only what changed since yesterday.”
The changes, not another full backlog dump.
“From this meeting’s action items, check Jira for duplicates, then draft one issue per owner with the deadline and a link to the notes.”
He asks when something is unclear and returns the issue numbers once you approve.
“Check today’s release and the linked GitHub pull requests. Draft comments on the related Jira issues with the version, then move fixed bugs to Done.”
One receipt shows the Jira and GitHub actions together.
“Find Jira issues tied to open enterprise promises in HubSpot. Flag any with no owner or due within 14 days.”
Jira knows delivery. HubSpot knows the customer. No second spreadsheet.
“Sum up unresolved high-priority issues in the 4.8 release and call out any whose Jira status doesn’t match GitHub.”
Read only, until you ask him to fix the mismatch.
Notes on any call, then tickets from the action items.
On Mac and Windows, the HeyBob app takes notes on any call with no bot joining, on Zoom, Google Meet, Microsoft Teams, Webex or Slack huddles. Every action item has Have Bob do it, Add to my to-dos and Skip. Tap Have Bob do it on “file the export bug” and he searches Jira, drafts the issue and asks before he files it.
Connected in a minute.
Tell Bob to connect Jira.
Open the Connect Jira button he posts and sign in with Atlassian.
Choose your Atlassian site and approve what he can reach.
Come back and say “retry.”
This is for Jira Cloud. Jira Data Center and Jira Service Management have their own separate connections that sign in differently, so name the exact product if yours is not standard Jira Cloud.
Jira is one shared connection. Give it a small role.
Today the Jira connection is shared by the whole workspace, so any job in your HeyBob workspace can use it. The safest setup is a dedicated Jira account with only what Bob needs.
- Browse only the projects he reports on.
- Create issues only where he should file work.
- Edit, comment and move issues only for the jobs you plan to hand him.
- Skip admin rights unless the job really needs them.
He shows you every change first.
Searching and reading run on their own. Creating an issue, editing a field, commenting or moving an issue asks first unless an admin has chosen otherwise. Be careful with Always allow: for Jira it covers all of his Jira actions, not just one. Start with one report or one triage job, check the first results, then loosen.
- Custom stays custom. Required fields and workflow rules differ by project.
- The account sets the limits. An over-powered Jira account stays over-powered.
- He reports what really happened. If Jira refuses a change, he says so instead of claiming it worked.
Common questions.
What can Bob do in Jira?
Search issues, report on projects, create issues, change fields, add comments and move issues through your workflow, within the connected account’s permissions.
Does Bob work with Jira Cloud or Jira Data Center?
The main connection is Jira Cloud. Jira Data Center and Jira Service Management have separate connections that sign in differently.
Does Bob ask before changing Jira?
Yes, by default. Reading runs on its own. Creating, editing, commenting on or moving an issue asks first unless an admin chooses otherwise.
Whose permissions does Bob use in Jira?
The connected Jira account’s. Jira is one shared connection for the workspace today, so connect a dedicated account with only the project permissions Bob needs.