> For the complete documentation index, see [llms.txt](https://docs.enate.net/whats-new/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/whats-new/older-versions/changes-overview-older-versions/2023.2-changes-overview/better-work-item-tracking-data.md).

# Better Work Item Tracking Data

We've also added some more information to Work Item screens to help make tracking of activity clearer:

#### Better Display of 'Reopened' events 

In the Work Item Timeline, there's now explicitly called-out entries to show when is has been Reopened from a Resolved state, showing when it was Reopened and by whom.

<figure><img src="https://1296463846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8xJkS0SKlesb8bmVBtGc%2Fuploads%2F63vD0EQtI4rdH2uxSeRJ%2FReopened1.png?alt=media&amp;token=30620ad7-4a8a-453a-b625-e14fe261d25d" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Note: Reopening of a Work Item via email will show 'System' as the 'Last Reopened By' value, so in the timeline filter the **'Include System-Generated Activities'** option should be enabled in order to view the complete timeline for reopening activities. To view 'Reopened' timeline entries if a work item was reopened by an agent, make sure the 'status changes' option from the timeline filter is enabled.
{% endhint %}

The information about who last Reopened it and when is also shown explicitly on the Work Item Info card.

<figure><img src="https://1296463846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8xJkS0SKlesb8bmVBtGc%2Fuploads%2F3ukCyrNv3PbcgtTksyIe%2FReopened2.png?alt=media&amp;token=2e1267f2-1db9-4765-be7f-2cc1534318e6" alt=""><figcaption></figcaption></figure>

#### More Information about State Changes

When a Work Item changes state, you'll now see not only the state it was changed TO, but the state it was changed FROM also. State texts will also show in the color of relevant states also.

<figure><img src="https://1296463846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8xJkS0SKlesb8bmVBtGc%2Fuploads%2F0cFN0OBtC1KXFmtikjrj%2FState%20Changes.png?alt=media&amp;token=f290ea08-2aaf-4f0a-85f0-ec7fcfeedd75" alt=""><figcaption></figcaption></figure>


---

# 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.enate.net/whats-new/older-versions/changes-overview-older-versions/2023.2-changes-overview/better-work-item-tracking-data.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.