Two questions are hard to answer by clicking: “which projects actually use this field?” and “is anything still using it if I delete it?” On an instance with dozens of fields and hundreds of projects, opening every field’s contexts one at a time is not a plan.
The app answers both in one call.
The endpoint
{baseUrl}/rest/jibrok/timeinstatus/1.0/migration/fieldContexts
For every context of every Time in Status, Timer and Stopwatch field, the response gives the projects and the issue types that context covers.
That is the inventory: field → context → where it is in force.
Open it in a browser while signed in as a Jira administrator, or call it from a script with your usual authentication. It lives under the app’s REST API, so if a call of yours is rejected by the XSRF check, see REST API - XSRF and the X-Atlassian-Token header.
migration/ because that is what it was built for, but nothing about it is migration-specific. It is equally the right tool for an audit or a cleanup on an instance that is staying on Data Center.
What to use it for
Before a migration
Migration from Data Center to Forge Cloud recreates each field in Cloud and attaches it to the same projects and issue types. Pull the inventory first and you get, up front:
- the complete list of fields that have to exist on the other side - no field discovered late because one project still used it;
- the projects and issue types per context, which is exactly what has to be reproduced in the Cloud contexts;
- an answer to “do we migrate this one at all?” for every field, before any of them are created.
Keep the response. After the migration it is the checklist you verify against: every context in the inventory should have a matching context, and a bound configuration, on the Cloud side.
Before a cleanup
Fields accumulate. Before deleting one, check the inventory for it:
- No contexts, or contexts covering no live projects - safe to retire.
- Contexts covering projects still in use - find out who relies on it first. A field that is deleted out from under a saved filter, a dashboard gadget or a report takes them with it.
When troubleshooting “the field is not on my issue”
A field is only rendered on an issue whose project and issue type fall inside one of the field’s contexts. The inventory tells you in one place whether the issue’s project is covered at all - the first thing to check on the Jira side of The field does not appear or is empty.
How to work with the result
The response is JSON, so the practical shape of the work is:
- Pull it once and save it - it is the state of the instance at that moment, and worth keeping next to the migration or cleanup ticket.
- Flatten it to one row per (field, context, project, issue type). A flat table is what makes it reviewable: sort by project to see what a project depends on, sort by field to see a field’s blast radius.
- Diff it after the change. Re-pull after a migration or a cleanup and compare - anything that disappeared and should not have is visible immediately.
Related
- Migration from Data Center to Forge Cloud - the full migration protocol; the DC Migration page is the UI over the same data.
- Time in Status REST API Reference - the rest of the app’s API.
- The field does not appear or is empty - the checklist this inventory feeds.

