Creating Issues

Creating Issues

Quickly turns a conversation into a properly filled-in issue, which is usually the difference between a ticket someone can act on and a one-line note nobody understands next week.

The Simplest Version

From a thread where the problem was discussed:

@Quickly create a bug from this thread

Quickly reads the whole thread, drafts a summary and a description from it, and creates the issue. If it does not know which project to use, it asks.

Giving It the Details

Every field you name is a field Quickly does not have to guess:

@Quickly create a bug in MOBILE, High priority, about the Safari login crash, and label it regression

That request supplies four things Quickly would otherwise infer or ask about:

About Priority Names

Jira's default scheme uses Highest, High, Medium, Low, Lowest. If your team says "P1", Quickly maps it onto whatever scheme your project actually uses, but naming the priority as your Jira instance defines it is the reliable route.

Issue Types

Available types come from your project's issue type scheme, not a fixed list in Quickly. Bug, Task, Story, and Incident are common, but a project configured with custom types accepts those instead. Ask @Quickly what issue types are available in MOBILE? if you are unsure.

Assigning at Creation

@Quickly create a task in MOBILE for the SSO migration and assign it to sarah@example.com

Assignment is resolved by searching your Jira users for the name or email you gave. If the search is ambiguous, Quickly tells you rather than picking one.

Creating Several at Once

For a discussion that produced a list of separate pieces of work, ask for them together:

@Quickly create tickets in MOBILE for each of the four follow-ups in this thread

Quickly creates them as a batch and reports each key it produced.

Approval Before Creation

Creating an issue is a write action. In Conservative mode every one of these requests pauses for approval, showing the fields it is about to send before anything reaches Jira. In Balanced mode single-issue creation runs automatically while bulk creation still asks. See Autonomy Controls and Safety.

What Gets Recorded

Every created issue appears in Action Logs with the tool call, the outcome, and a direct link to the issue. If a creation fails, the log holds the error the tracker returned, which is normally enough to see whether it was a permissions problem or an invalid field.