# Issues

_Applications › Issues_

![Issues](https://atloriaassets.blob.core.windows.net/assets/a438221c-c1af-407c-b9e6-a56c986db846/93ba8f3ad2a51ed3f53d7b4298ebe355.png#atloria-annotations=%7B%22annotations%22%3A%5B%7B%22type%22%3A%22box%22%2C%22x%22%3A1.06%2C%22y%22%3A15.01%2C%22w%22%3A1.48%2C%22h%22%3A3.62%2C%22label%22%3A%223%20%20Status%22%7D%2C%7B%22type%22%3A%22box%22%2C%22x%22%3A67.15%2C%22y%22%3A15.01%2C%22w%22%3A10.96%2C%22h%22%3A3.62%2C%22label%22%3A%224%20%20Add%20filter%22%7D%2C%7B%22type%22%3A%22marker%22%2C%22n%22%3A4%2C%22x%22%3A72.63%2C%22y%22%3A16.82%7D%5D%7D)
*issues*

![Status](https://atloriaassets.blob.core.windows.net/assets/a438221c-c1af-407c-b9e6-a56c986db846/935801a8f6fb5ec73d052edf4c1975e3.png)

![Add filter](https://atloriaassets.blob.core.windows.net/assets/a438221c-c1af-407c-b9e6-a56c986db846/86b50fe7450b68563b0ce5e7088b922a.png)

## Overview

Issues are tracked work items, problems, requests, or tasks within a Project. Use the Issues area to review work relevant to you, focus the list by Status or other criteria, organize the information shown, and export the current results when required. Project managers, Project team members, Issue reporters, and administrators use these views to monitor and locate accessible Issues.

## Workflow

### Decide which personal Issue scope to review

Choose a predefined view when you need to start with Issues related to your own work rather than all accessible Issues. Each view changes the current list scope; it does not change the Issue records.

1. In the application navigation, select the personal Issue view that matches your purpose:
   - Select **Issues assigned to me** to display Issues assigned to your account.
   - Select **Reported issues** to display Issues that you reported.
   - Select **Updated issues** to display recently updated Issues.
   - Select **Watched issues** to display Issues that you are watching.

2. Review the displayed Issue list before applying further criteria. If the selected view is not the scope you need, choose a different personal Issue view and review that list instead.

> **Tip:** Start with a personal view when you need to act on work connected to your account. This avoids applying unnecessary criteria to a broader Issue list.

### Decide whether to narrow or organize the current list

After selecting a personal or Project-specific Issue list, decide whether the current results are already sufficient. Use the Status criterion and additional filters to focus the list, then review the columns and grouping used to present the results.

3. To limit the list by its current state, use **Status** and select the required Status criterion.

4. If Status alone does not provide the required scope, select **Add filter** to add another criterion and further narrow the displayed Issues.

5. To review the information shown in the list, examine **Selected Columns**, which identifies the fields currently displayed. Review **Available Columns** to see the fields that can be added to the Issues list.

6. When the list is easier to review by category, use **Group results by** to organize the displayed Issues into groups. Available grouping choices shown in the Issues view include Project, Tracker, Status, Priority, Author, Assignee, and Category.

7. Review the resulting list. If it is too broad, return to **Status** or **Add filter** and refine the criteria. If it is too narrow, revise the criteria so that the required Issues are displayed.

> **Note:** Filtering, column selection, and grouping affect the displayed Issue list. Review the final results before exporting them or opening an Issue.

### Decide whether to export the displayed Issue information

Export only after the displayed list contains the Issues and fields required by the receiving system or recipient. The export uses the current displayed Issue information.

8. Review **Selected Columns** and confirm that the list shows the information required for the export.

9. Set **encoding** to the character encoding required by the receiving system.

10. Set **field_separator** to the separator required between exported fields.

11. Select **Export** to export the displayed Issue information.

12. If the exported information is not suitable for the receiving system, return to the Issue list, revise the filters or displayed columns, review **encoding** and **field_separator**, and select **Export** again.

> **Warning:** Confirm the current filters and Selected Columns before selecting **Export**. The export contains the displayed Issue information, so an overly broad or incomplete list can produce an unsuitable file.

### Decide whether to open an Issue from its Project

Use the Project route when you know the Project that contains the Issue. This route starts from the Projects list, opens the selected Project, and then opens its Issue list.

13. Select **Projects** to open the list of Projects that you can access.

14. Select the required **Project name** to open that Project.

15. Select **Issues** to open the selected Project’s Issue list.

16. If needed, use **Filter** to narrow the displayed Issues.

17. Select the required **Issue subject or Issue identifier** to open the Issue record.

18. If you cannot locate the required Issue, return to the Project’s Issue list and revise the **Filter** criteria, or confirm that you have access to the Project and Issue.

## Examples

A Project manager needs to provide a list of recently updated Issues for a Project team review.

1. Select **Updated issues** to display recently updated Issues.

2. Use **Status** to focus the list on the Status required for the review.

3. Select **Add filter** if the Status criterion does not sufficiently narrow the results.

4. Review **Selected Columns** to confirm that the displayed list contains the information needed by the team. Check **Available Columns** if additional fields are needed in the list.

5. Use **Group results by** and select Project so that the team can review Issues by the Project to which they belong.

6. Set **encoding** and **field_separator** according to the requirements of the system or recipient that will receive the exported information.

7. Select **Export** to export the displayed Issue information.

If the manager instead needs to inspect one Issue in a known Project, the manager selects **Projects**, opens the required **Project name**, selects **Issues**, optionally uses **Filter**, and then selects the relevant **Issue subject or Issue identifier**.

## Tips

> **Tip:** Use **Group results by** when comparing Issues across Projects, Status values, priorities, authors, assignees, trackers, or categories.

> **Note:** **Available Columns** identifies fields that can be added to the Issue list, while **Selected Columns** identifies fields currently shown in the list.

> **Warning:** Access to a Project does not by itself guarantee access to every Issue. You must have access to the selected Project and the Issue that you want to open.

## Troubleshooting

| Symptom | Likely cause | Fix |
|---|---|---|
| The required Issue is not displayed in a personal view. | The Issue may not be assigned to you, reported by you, recently updated, or watched by you. | Select the personal view that matches your relationship to the Issue, or open the Issue from its accessible Project. |
| The Project does not appear after selecting **Projects**. | The Project is not available to your account. | Confirm that you have access to the required Project. |
| The required Issue cannot be found in a Project’s Issue list. | The list may need to be narrowed, or you may not have access to the Issue. | Use **Filter** to focus the Project Issue list and confirm that you have access to the Issue. |
| The exported file cannot be accepted by the receiving system. | The system may require a different character encoding or field separator. | Review and set **encoding** and **field_separator** before selecting **Export** again. |

## Related pages

- [issues — Overview](https://redmine-rails-fixture.atloria.app/p/redmine-rails-fixture-jECuEDWkc3/user/issues-overview)
- Issues — Learning Path
