> For the complete documentation index, see [llms.txt](https://docs.aqua-cloud.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aqua-cloud.io/documentation/items/general-item-capabilities/print-item-data.md). # Print item data Print all data for any open item easily using the Print button in the ribbon. get a complete, formatted overview of item details in one click. In the ribbon of an open item, you can use the Print button to print all the information about that item.

Print action within the ribbon of the item

You can print the details, i.e. all fields as well as the description, the attached files, the history and dependencies. In addition, you can print the test steps for test cases, the test cases for test scenarios and the [discussions](/documentation/items/general-item-capabilities/discussions-comments.md) for requirements, test cases, test scenarios and defects. --- # 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.aqua-cloud.io/documentation/items/general-item-capabilities/print-item-data.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.