> For the complete documentation index, see [llms.txt](https://docs.meta-inf.hu/glass-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meta-inf.hu/glass-documentation/general-product-information/concept-and-goals.md).

# 💡 Concept & Goals

{% embed url="<https://www.youtube.com/watch?t=3s&v=kI502kFkRs8>" %}
Improve your project documentation in Jira
{% endembed %}

## Goals and Proposal <a href="#id-concept-and-motivation-motivationandgoals" id="id-concept-and-motivation-motivationandgoals"></a>

With Glass Project Documentation our goal was to solve three crucial problems with Jira Project Configurations:

* to help **new users** **learn** about Jira project settings
* to give more control to **admins** in regards to **validating settings**
* to provide accurate and summarized information for **audits**

In the below table we would like to share our proposal with you for achieving these goals:

| **Goal**                                              | **Problem**                                                                       | **Outcome**                                                                                                                                                  |
| ----------------------------------------------------- | --------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| <p><strong>Education - for Newcomers</strong><br></p> | Helps (new) users to quickly catch up with (new) Jira Projects.                   | <ul><li>Enthusiastic users</li><li>Increased productivity</li><li>Easier communication with Administrators</li></ul>                                         |
| **Control - for Admins**                              | Helps Jira administrators to quickly validate Project Schemes and other Settings. | <ul><li>Less administrative mistakes</li><li>Easier cooperation for instances with multiple Administrators</li><li>Easier communication with Users</li></ul> |
| **Process Documentation - for Audits**                | Creates and keeps Project Configuration Documentation updated                     | <ul><li>Saves time and effort</li><li>Keeps documentation up-to-date</li><li>Easy to understand format</li></ul>                                             |

## Concept <a href="#id-concept-and-motivation-concept" id="id-concept-and-motivation-concept"></a>

To reach our goals, we created an app that provides tons of information not only for **Jira administrators** but for the **average user** as well. To make this happen, we've made all information accessible for users with the [Glass View permission](/glass-documentation/user-guides/administration-guide/2-granting-permission.md).

With Glass Project Documentation Administrators can "open" most of the projects for a wide range of users, while still keeping **data-sensitive projects** hidden via Permission Schemes.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.meta-inf.hu/glass-documentation/general-product-information/concept-and-goals.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.