> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/platform/guides/operations-guide/jira-ticket-creation.md).
# Jira Ticket Creation
This doc is about creating Jira ticket.
### What are Jira Tickets?
A ticket in Jira,is an event that must be investigated or a work item that must be addressed.In Jira Service Desk,tickets entered by a customers are called requests.Within a Jira Service Desk queue or in Jira Software, a request is called an issue.
### Steps to create Ticket in Jira.
**Step 1:** Open the Jira Software.
**Step 2:** Search for the respective Project in which you want to raise a ticket or the project which needs to address your ticket ,in the Search bar.
**Step 3:** Now click on the ' Create', a pop-up apears on the screen as shown below and fill the respective details.Once all the details are entered ,click on the create button below. Now the ticket is raised in the main page of the project you have chosen and will be addressed .
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.digit.org/platform/guides/operations-guide/jira-ticket-creation.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
