Jira issues

1. Tag #jira
2. Tap Create
3. Gemini writes it up
4. Issue in Jira
5. Note + #in-jira

Gemini turns the idea and its notes into a ticket: a summary, context, the proposal, acceptance criteria, open questions, labels and a priority. Your idea is quoted at the bottom, with a link back to it.

Setup, once: an Atlassian API token and a rule in Idea Bucket. Jira Cloud only (yourcompany.atlassian.net).

#Create an API token

1. Open Atlassian API tokens and sign in with the account that should create the issues.

2. Select Create API token, name it Idea Bucket, pick an expiry, then Create.

3. Copy the token. You won't see it again.

The issues are created as that Atlassian account, so it needs permission to create issues in the project.

#Create the rule

1. In Idea Bucket, open Profile → Automations → New rule.

2. When: Gets a tag, tag jira. Do this: Create Jira issue.

3. Fill in Jira site (yourcompany.atlassian.net), Atlassian email, API token, Project key (like ARGU) and Issue type (Task, Story, Bug, Epic or your own).

4. Optionally tell Gemini how to write it, like "Write it as a user story with acceptance criteria", then Save rule.

5. Open the rule with Edit and select Test connection. Connected as … · ARGU (Argu) means it works.

All rule fields

Field	What to enter
Jira site	Your Jira Cloud address, like argu.atlassian.net. A full URL is fine; only the site is kept.
Atlassian email	The email of the account the token belongs to.
API token	Saved where only the automation can read it, never shown again; later the field shows Token saved · Replace.
Project key	The letters before issue numbers, like ARGU in ARGU-142.
Issue type	Must exist in the project. Default Task.
Ask Gemini to	Optional, up to 1,000 characters.
Add a tag	Added to the idea once the issue exists. Default #in-jira; empty adds none.
Archive the idea	Off by default. On: the idea is archived once its issue exists.
Auto-accept requests	Off by default. On: no Create prompt, the issue is created right away.

#Approve or auto-accept

When the rule fires, the idea's card asks Create a Jira issue?

• Create: Gemini writes the ticket and it's created in Jira. The idea gets a note like "🎫 Created ARGU-142 · Add CSV export of ideas" with the link, and #in-jira.
• Not now: nothing is sent; the run is Skipped ("Not sent").
• No answer in 14 days: Skipped ("Expired").

With Auto-accept requests on, every #jira idea goes straight to Jira, and the note says "(auto-accepted)". Recent runs shows Created ARGU-142 · auto-accepted with Open in Jira.

Details

• Each rule creates one issue per idea. Retry on a failed run never creates a second issue: once Jira has answered with a key, the run keeps it.
• If Gemini isn't available, the issue is still created: the first line of the idea becomes the summary and the idea is the description.
• Labels are Gemini's suggestions plus the idea's tags, as Jira labels (lowercase, no spaces).
• If the project doesn't allow setting a priority, the issue is created without one.
• Each run counts as one automation run and one AI run toward your hourly limits.

#When it fails