How panel visibility works
Stopwatch Field (Forge) provides one issue panel:
- Stopwatch panel - stopwatch state and time
By default, no panels are visible. You need to enable them for the projects and issue types where you want them to appear.
Panel visibility is controlled through two Jira properties:
- App level - the app property
tis-cloud-panelsapplies to all projects (global default) - Project level - the project property
tis-cloud-panels-stopwatchenables the panel for a specific project
The project property key belongs to Stopwatch Field alone, so other JiBrok time-tracking apps installed on the same site do not change its panels.
The visibility property
Both properties are JSON objects with the same key:
{
"sw": ["10001", "10002"]
}
| Key | Panel |
|---|---|
sw |
Stopwatch panel |
The value is an array of issue type IDs for which the panel should be visible:
["*"]- visible for all issue types["10001", "10002"]- visible only for specific issue type IDs[]or key absent - not visible
Configuring visibility
From the admin panel
The app provides a way to manage panel visibility from the admin panel. When you configure web panels on the Stopwatch tab, the app automatically syncs the visibility settings.
Visibility is updated every time a panel configuration is saved or deleted.
Sync panel visibility
Sync panel visibility (Admin page > Health Check) checks every project of the site and removes leftovers of this app only: a project can keep the panel visibility of an earlier installation of the app (for example, after the app was removed and installed again) while the app has no panel configuration for it - the panel then shows up empty. Other panels configured for the project stay. Check an issue on the Health Check tab tells when a sync is needed.
On a site with many projects one click may not reach every project in time - then the tab says: “Not every project was checked for leftover panel visibility in time. Click “Sync panel visibility” again to continue.” Click it again until the message no longer shows.
Several apps on one site
A panel limited to some projects shows there because the app marks these projects in a project property. Time in Status, Timer and Stopwatch each keep their own property, so panels of one app never turn on or off the panels of another app installed on the same site, and Sync panel visibility in one app leaves the other apps’ panels as they are.
How the display condition works
The app uses Jira’s displayConditions.jiraExpression to check visibility. For each panel, Jira evaluates:
- Does the project have a
tis-cloud-panels-stopwatchproperty with theswpanel enabled for this issue type? - Does the app have a global
tis-cloud-panelsproperty with theswpanel enabled?
The two checks are joined with OR: if either passes, the panel is displayed. The project level cannot hide a panel that the app level enables.
Examples
Enable the Stopwatch panel for all projects
Set the app-level property tis-cloud-panels:
{
"sw": ["*"]
}
Enable the Stopwatch panel only for Bug issue type in a specific project
Set the project-level property tis-cloud-panels-stopwatch for that project:
{
"sw": ["10001"]
}
Where 10001 is the issue type ID for Bug.
Tips
- Web panels vs panel visibility: Creating a web panel in the admin panel defines what the panel shows (which events start, pause and stop the stopwatch, calendar, format). Panel visibility controls where it appears (which projects and issue types). You need both.
- Issue type IDs: To find issue type IDs, go to Jira Settings > Issues > Issue types, and check the URL when clicking an issue type.
- Changes may be cached: Jira may cache panel visibility. Changes usually appear within a few minutes. Refreshing the issue page can help.

