Has anyone created Copilot Prompts to create JIRA Epics?

Hi @Bashaw_ Bryan 

Welcome to the community!

When using Copilot to create Jira Epics, the key is to align your prompt with how Epics are already structured in your Jira projects, rather than relying on free-form text.

A few practical guidelines that tend to work well:

• Base the prompt on your standard Epic template (Epic name, summary, problem statement, scope, out of scope, success criteria).

• Be explicit about field names used in Jira (for example: Epic Name, Description, Labels, Components), as Copilot responds better when the structure matches Jira fields.

• Provide business context first, followed by expected outcomes and high-level deliverables. This helps generate Epics that are usable beyond just a title and description.

• Treat Copilot output as a first draft and refine it to match internal delivery and governance standards before uploading to Jira.

You can also refer some articles around how copilot works together with Jira for better understanding:

• Unlock productivity with Jira Cloud plugin for Microsoft Copilot for Microsoft 365 
• Integrate the Jira Cloud plugin for Copilot in Microsoft Teams 
• How to integrate GitHub Copilot with Bitbucket, Jira & Confluence 

Kind Regards
Utkarsh